Welcome to the encoding guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue. These guidelines describe the methodology used to create TEI XML files for describing Syriac manuscripts according to the schema implemented by Syriaca.org in the project Syriac Manuscripts in the British Library. For the moment, these guidelines cover only the description rather than the transcription of manuscripts. Syriaca,org hopes to expand these guidelines to include transcription in the future. We have chosen to use the TEI guidelines because they allow both a high level of detail and flexibility. We anticipate that this schema can be easily adapted for other Syriac manuscript catalogues and we invite comments and suggestions for improvement.
These guidelines are based on the following sources. The general editors began by following the encoding guidelines for the Fihrist Union Catalogue of Manuscripts from the Islamicate World and the ENRICH TEI P5 ODD, which were then modified by Syriaca.org into a Syriaca TEI for MSS Manual (now deprecated), in turn these encoding guidelines were updated to be largely compatible with the Consolidated TEI P5 Customization and Encoding Guidelines for Manuscript Description for western medieval manuscripts jointly created by Cambridge University Library (James Freeman, with Suzanne Paul) and the Bodleian Library (Matthew Holford) with contributions by Andrew Dunning (formerly British Library) and James Cummings. (Those consolidated guidelines in turn draw in places on earlier western medieval manuscript guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.)
It is essential to note that we have customized these guidelines specifically for use in digitally encoding the manuscript descriptions made by William Wright in his Catalogue of Syriac Manuscripts in the British Museum (3 vols., 1870-1872). Due to this specialized use, these guidelines do not include all possible TEI XML features which might be desired for cataloguing Syriac manuscripts in general. For example, because Wright does not provide detailed descriptions ofmodern custodial history of the manuscripts we have not utlized those features in these guidelines. Similarly, because the main language of Wright's catalogue is English, these guidelines assume that each file will have English as its main language.
In addition, we have followed the guidelines below with the assumption that the resulting XML files for the Syriac Manuscripts in the British Library project (hereafter SMBL) will be displayed using the custom Srophe App developed by Syriaca.org. We have also made an effort to ensure compatibility (as much as possible) with the HTML tools and transformations developed for the Consolidated TEI P5 Guidelines for Manuscript Description.
Phrases or words in other languages than English are tagged by adding the xml:lang attribute to the element enclosing the text, or where no other element is available with a <foreign> element and a xml:lang attribute.
By default the Srophe App will display text in the <foreign> in italic unless it is marked as Syriac, in which case additional right-to-left formatting will be applied. For a list of allowed language attribute values see below.
A text node is not required for many uses of <locus> (such as when it is used nested in an <msItem>), but least one attribute value must also be encoded with every <locus>, either from or to or both. (Since Wright's catalogue does not often give ending ranges, the to occurs less in the data). These attribute values may be used in the future to enable links to folio images or calculation of lengths of manuscript items. Frequently in Wright’s catalogue the beginning location of a manuscript item is given, but not the ending location. In this situation, our policy is to record only the listed opening location in Wright’s catalogue as the beginning of the range in the attribute from. We do not supply a to attribute unless Wright has indicated on what folio the msItem ends, for example by citing an <explicit> or <finalRubric>.
Deprecated Practices and Legacy Data:
As a legacy of an earlier encoding model, the SMBL data contains some folio ranges encoded as numerals in to without "a" or "b". In this earlier data model, we attempted to deduce the end of ranges for manuscript items when not specified by Wright. Similarly when Wright's prose indicated that his description applied only to a single folio (for example when describing a marginal note), our policy was previously to list that location in both from and to attributes. After 2022, we ceased to encode in this way. While we have left these estimates in the data, documents revised since 2022 longer add estimated data in this way.
Divergences from Consolidated Schema:
In SMBL we have assumed that <locus> refers to a folio or folio range unless otherwise indicated. Accordingly, we do not use the scheme attribute to indicate the foliation scheme except in cases where the <locus> refers to something other than a folio, such as a column.
One of the distinctive features of SMBL is that we have integrated our catalogue with the reference works published by Syriaca.org in order identify the following entities: persons, places, literary works, citations of published bibliography, and references to manuscripts. For each of these entity types, Syriaca.org has published an ‘authority file’ which assigns a URI or Uniform Resource Identifier to every unique entry. These authority files include The Syriac Biographical Dictionary, The Syriac Gazetteer, The New Handbook of Syriac Literature , and A Comprehensive Bibliography on Syriac Studies, in addition to Syriac Manuscripts in the British Library.
In these authority files, each entity is an individual abstract concept identified by a unique URI. For example, the person known as Ephrem the Syrian is identified by the URI: http://syriaca.org/person/13 and the city of Edessa where he spent much of his life is identified as http://syriaca.org/place/78. The necessity of using unique strings of characters instead of traditional names arises from the occurrence of homonymous entities. For example, The Syriac Gazetteer has entries for 69 different churches and monasteries each with the name ‘Mar George’. Accordingly, all Syriaca.org URIs are unique—each identifying only one conceptual entity. Thus, every ‘Church of Mar George’ is assigned a separate URI.
Syriaca.org URIs are not merely random strings of text and numbers; they are HTTP URIs, meaning that each URI is also a URL (a Uniform Resource Locator, e.g. an HTTP address). Thus, Syriaca.org’s URI for Ephrem the Syrian, http://syriaca.org/person/13, is also a valid HTTP address. The benefit of using HTTP URIs is that these URIs are ‘self-descriptive’ in that each URI is also an HTTP link to a web document describing or defining the concept identified by the URI. Although perhaps obvious to state, the web document which is returned from a Syriaca.org URI is only a definition of the concept named by the URI, not the entity itself (thus the address http://syriaca.org/place/78 does not allow one to download the real-world city of Edessa, but a web page describing that city!).
In the Syriaca.org data model, each URI represents a conceptual thing with a mental existence related to, but not reducible to, its historical or physical manifestation. Syriaca.org adopted this broad definition so that mythological and other ahistorical persons, places, and concepts can be assigned URIs. For example, the concept identified by the URI http://syriaca.org/person/13 identifies not only the historical person Ephrem the Syrian, but also the supra-historical hagiographical and pseudepigraphal traditions about him. Following this same logic, any historical concept can be described in the Syriaca.org URI model, even if its historical existence was only in the cultural imaginary.
The Syriaca.org authority files and URIs are central to the data model of SMBL, accordingly the sections below describe in greater detail how we have encoded these entities throughout the data.
Deprecated Practices and Legacy Data:
Divergences from Consolidated Schema:
Because Syriaca.org already provides an integrated authority file for persons using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema. We also do not use the element <orgName> since it is not a useful entity for our historical data, instead Syriaca.org uses the <persName> element in a slightly broader manner than the TEI guidelines. A <persName> element may be used to refer to a name for a single person or a group of persons.
As a general rule place names have been tagged with either <origPlace> or with <placeName>, for example when they occur inside in any descriptive element such as <note>, <handNote>, or an <item> in <additions>. In most cases, the place name is wrapped with the element <placeName> and the language(s) of the name supplied with attribute xml:lang. Exceptions to this rule are as follows:
Our policy is to report the place names in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the spelling or name used by Wright is no longer commonly used in scholarship.
Divergences from Consolidated Schema:
Because Syriaca.org already provides an integrated authority file for places using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema nor do we include the nested information in <origPlace> such as <country>, <region> and <settlement>. These relationships can be found separately in The Syriac Gazetteer.
As a general rule references to titles of literary works have been tagged in one of two methods.
Our policy is to report the references to works in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the form used by Wright is no longer commonly used in scholarship.
Divergences from Consolidated Schema:
Because Syriaca.org already provides an integrated URI authority file for works using Syriaca.org URIs, we do not use the key attribute recommended by the Consolidated Schema.
Citations of printed biblographic items (books, articles, etc.) have been tagged with the <bibl> element. These citations can be found in two places:
In both cases, the bibliographic citation may be linked with a URI by using a child element <ref> with the URI is placed in a target attribute on <ref>. At present the state of authority control for Syriac bibliography is incomplete. Accordingly, we have only encoded URIs for bibliographic citations when available. Currently we rely on two sources of URIs. Some citations are linked with uris of the format ‘http://syriaca.org/bibl/8’ from Syriaca.org. Others are marked with URIs from The Comprehensive Bibliography on Syriac Studies of the format ‘https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library’. In a future development, all of these citation URIs will be merged to a format of ‘http://syriaca.org/cbss/WMADLJWW’.
Our policy is to report the references to bibliography in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform citation where the form used by Wright is no longer commonly used in scholarship.
Cross-references in the description to other manuscripts should be enclosed in <bibl> tags with type of value MS. When possible the cross-reference may also be linked linked with a child <ptr> element with target attribute pointing to the URI for the other manuscript.
Our policy is to report the references to manuscripts in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform shelfmark where the form used by Wright is no longer commonly used in scholarship.
We have avoided marking up formatting using the <hi> element. The element <lb> has been used to indicate line breaks when Wright provides transcriptions of Syriac or Arabic text.
In a few rare cases, ‘camelCase’, has been used for attribute values forming more than one word in natural language.
Divergences from Consolidated Schema:
SMBL has prefered to use a hyphen rather that camelCase for attribute values longer than one word in length.
The <rubric>, <incipit>, and <explicit>, and <quote> elements are used to encode Syriac text transcribed from the manuscripts. The have been reproduced verbatim from William Wright's catalogue. Caveat lector! Transcriptions have not been re-checked against the original manuscripts. In addition, the <quote> element has been used to encode prose (in any language) which Wright marked with quotatoin marks (e.g. inverted commas).
For the sake of clarity, the SMBL editors have expanded abbreviations in Wright's prose using the nesting elements <choice>, <abbr>, and <expan>.
In rare cases, we have indicated damage using the <damage> element and agent attribute.
ADD DISCUSSION OF SIC HERE
The <supplied> element has been used both for Wright's own editorial additions and for editorial additions to Wright's catalogue made by the editors of SMBL, ADD DISCUSSION OF SUPPLIED HERE
in rare cases, deletions by the scribe or later annotators which are reported by Wright have be recorded using the <del> element.
Questionable or partly legible readings should be marked with <unclear> (generates a ‘(?)’ after the text in html)
Line beginnings should be indicated with empty <lb> elements, column beginnings with empty <cb> elements
Quotations from the manuscript, outside of elements such as <incipit>, <explicit> and so on, should be enclosed in the <q> element. This may have attribute type with sample values:
The TEI root element contains a declaration of the TEI namespace, a language declaration, and a unique identifier for the manuscript.
The xml:lang value indicates the language of Wright's manuscript description (and thus the language of file as a whole) and should always be marked as English (‘en’) in every file.
The <TEI> element itself takes an xml:id attribute whose value is constructed from the unique identifier for the XML file and the top level manuscript described in that file. In the example above, the file ‘1.xml’ (which contains manuscript https://bl.syriac.uk/ms/1) has the following xml:id on the root TEI element: ‘manuscript_1’.
Divergences from Consolidated Schema:
SMBL diverges from the consolidated schema in the following ways:
The <fileDesc> element contains a <titleStmt>, <publicationStmt>, and <sourceDesc> element.
The <titleStmt> element summarizes the scope and authorship of the TEI file, and the cataloguing project of which it is a part, rather than for the manuscript itself (which is described in the <sourceDesc>). It must contain (1) a <title> element containing the manuscript shelfmark, (2) [for the medieval catalogue] a <title> element with type attribute of value collection describing the collection of which the manuscript is a part, and (3) one or more <respStmt> elements listing the person(s) responsible for the cataloguing and encoding. The <respStmt> element must have a xml:id attribute containing an identifier for the person(s) responsible for the cataloguing and/or encoding. The name should be recorded in a persName element (see 1.3.3.1. Personal Names) and the role of the person responsible in <resp> elements. If known, the date should be given in the when attribute of <resp>
The <titleStmt> is also the place to record any funding bodies which contributed to the cost of cataloguing. The <funder> element can contain a plain text statement or <orgName> elements. The websites of sponsors, and their logos, can be included. For example:
Ideally the @url attribute of the <graphic> element should point to an image hosted by the funding organization. The <graphic> element cannot be a child of the <funder> element, but must be enclosed in a <persName> or <orgName> element.
Contributions to the cost of purchasing the manuscript should be recorded as part of the Acquisition section of its history.
Where a description has been compiled from multiple sources, each source should be listed in the <respStmt>, and the elements of the description for which they are responsible should be identified using the resp attribute with value equivalent to that source's xml:id.
The <publicationStmt> summarizes the publication of the TEI document, rather than the manuscript itself (which is described in the <sourceDesc>). For union catalogues such as Fihrist, it should contain an <email> containing the address to which enquiries should be sent, and an <idno> of type marcOrg containing the MARC Organization Code of the institution (e.g. "UkCu" for University of Cambridge).
The <revisionDesc> element records ONLY major changes to the catalogue entry, such as re-dating or re-location, addition of provenance information, new identification of contents, etc. It must contain at least one change element, which must have the when attribute and may have the who attribute (which may be linked to the xml:id of the person in the <respStmt> element in 1.4. The TEI Header). The changes should be recorded in a reverse chronological order with the most recent change first.
In some catalogues, the fourth button in the header is "Subjects" rather than "Places". This is an index of subject classifications, using the Library of Congress subject heading and name authorities.
Keywords apply to the manuscript as a whole. You can associate each with one or more specific works by enclosing the <term> in a <ref> whose target attribute is a space-separated list of pointers to the xml:id values of <msItem> elements, prefixed with #.
Each <term> must have a key attribute containing the LoC authority entry identifier prefixed with "subject_". The text within the <term> element is also required, as this is what is displayed on the manuscript's page on the web site. It can be a variant of LoC's preferred term, if you think that more appropriate. If the term hasn't been used before, it will be automatically added to the web site the next time it is re-indexed.
The <sourceDesc> element contains a single child element, the <msDesc>. Within that is all the information about the manuscript as a physical object, its constituent parts, and intellectual works represented within.
All manuscript descriptions must be informed by attention to codicological units. In other words, whether the manuscript was created in one place, over one period of time, or is a composite of parts from multiple sources, assembled at a later date.
If the manuscript forms a single codicological unit, its intellectual content, physical description, and history should be described directly under the <msDesc> element. Individual works can vary in date or hands while still being of a single source. In such cases, add <note> elements to the <msItem> for each work, and an overview for the whole manuscript in <physDesc>, <history>, etc. Do not simply enter information (dates, dimensions, etc) as lists of <ref> elements.
If the manuscript comprises multiple codicological units, each should be described in its own <msPart> element, and only information common to the whole manuscript should be described directly under the <msDesc> element. This will typically include aspects of the physical description (e.g. extent, foliation, binding), aspects of history (notably provenance and acquisition), but possibly also some intellectual content (for example, if a table of contents for the whole volume was added by a later owner, or if the manuscript has replacement leaves). Conversely information relevant to each unit should be described in separate <msPart> elements.
Information about the current location and shelfmark of the manuscript should be given in the <msIdentifier> element using the following elements in the following order: <country>, <settlement>, <institution>, <repository>, and <idno> which must have type with value shelfmark.
The intellectual content of the manuscript or codicological unit should be listed in the <msContents> element.
The <summary> element can be used to provide a brief prose account of a manuscript's contents and significance, unless this has already been covered by the <head>.
In some cases the decision of which language is ‘main’ and which is/are ‘other’ may be rather arbitrary.
The attributes values used should conform to the BCP 47 standard (http://www.rfc-editor.org/rfc/bcp/bcp47.txt) which start with two-or-three-letter ISO 639 codes for languages, then an ISO 15924 code for the script, and finally IANA language subtags (https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) for other information, such as methods of transliteration.
If the unit contains multiple works, in different languages or scripts, the <textLang> element should be used in the <msItem> instead, q.v.
According to the conventions of the catalogue, languages may be encoded at a high or low level of granularity - for example, Middle English may be encoded as "enm" or as "en", Anglo-Norman French may be encoded as "fr" or "xno".
Current recommendations (July 2023) for cataloguers at Oxford and Cambridge are to encode languages to as granular a level as possible using the following codes:
| Latin | la |
| Ancient Greek | grc |
| Modern Greek | el |
| Old English | ang |
| Middle English | enm |
| English (after c. 1500); do not encode "Early Modern English" | en |
| Old French | fro |
| Middle French | frm |
| Anglo-Norman | xno |
| French | fr |
Guidance for other vernacular languages is under development.
The <msItem> element may be used:
As a general rule, each distinct item in the manuscript should be descibed in a distinct <msItem> tag.
Pages containing short notes or scribbles by later hands should be recorded in the <additions> element, see 1.6.4.7. Additions.
The Guidelines offer the following definitions: ‘each discrete item in a manuscript’; ‘an individual work or item within the intellectual content of a manuscript’. Often the identification of these works or items does not pose difficulties, but many more complex cases do occur.
A more helpful definition of a manuscript item may be ‘a complete work or item, or a self-contained part of a larger work with (potentially) independent circulation’. A ‘self-contained part of a larger work’ could be a letter in a letter-collection, or a sermon in a homiliary; it could also represent the biblical text or the commentary in a glossed biblical manuscript.
As a guiding principle, where possible and practicable the <msItem> element should be used to markup up the work as a whole, and its self-contained parts, and the nesting of the different <msItem> elements should express the relationship between part and whole.
Difficulties are posed by:
Recommended best practice is to catalogue and encode so that each item mentioned is discoverable. This can be achieved in different ways according to the information available. Suggested encodings for the above examples are:
For sample encodings of liturgical books (a Book of Hours) and a Bible, see the Appendix.
Treatment of these texts will vary according to the arrangement of text, gloss, and commentary; whether gloss and commentary are continuous; whether gloss and commentary are contemporary or later, and whether they form an integral part of the mise-en-page; whether there are multiple layers of gloss / commentary. Examples:
Significant added texts should be described in <msContents>, NOT in <additions>. Decision as to what is ‘significant’ will be a matter of judgement, but in general if the text is to be discoverable - if it is important for the text to be identified or described, or to have its rubrics / incipits recorded, etc. - it should be encoded using <msItem>. This may involve some reorganization of the description during retroconversion.
Two possible approaches are described here. Each may be appropriate in different circumstances, dependent for example on the nature of the manuscript and/or the nature of the description being converted:
The author name should be given in a standardized form. For retroconversion, use the form of the name given in the source text; for new cataloguing, use a standard form from the usual reference works.
If you are not responsible for maintaining the authority files, go to the web site, click the People button, and search to see if the same person already exists in another manuscript in the same catalogue, with the same or similar (or translated) name. If they have, set the key attribute to the identifier of the existing record, which is the part of the URL after the last slash, starting with "person_". If you can find the person by searching in VIAF (http://viaf.org/) set the value to "person_" followed by their VIAF number. Otherwise, leave the key attribute blank and an identifier will be assigned to it at a later date.
Where an author has multiple names (e.g. translations or transliterations) add these as child <persName> elements (with xml:lang attributes). Do not use <foreign> in this context. But the key attribute remains on the <author> element. Multiple <author> elements should be used for works with multiple authors (not other contributors, such as scribes, these should be added as <editor> elements with role attributes.)
(Optional) Either <author> or <persName> elements can contain <surname>, <forename> and <addName> child elements to divide up the full name as appropriate to naming customs (<addName> has a type attribute in which you can specify "laqab", "kunyah", "khitab", "nisbah”", etc.)
For secondary statements of responsibility, use the <editor> element, distinguished with a role attribute containing a three-letter code (or multiple codes separated by spaces) selected from the MARC relators list (https://www.loc.gov/marc/relators/relaterm.html). Do not add a label for their role, as this will be added when displayed on the web site. For example, for a translator:
In all other respects, <editor> elements can contain the same child elements as <author> (eg. multiple <persName> elements) and attributes (e.g. a key linking them to an entry in the persons authority file, so that they are indexed on the web site.) Further details about their role in the creation of the work can be explained in a separate <note>.
The title element provides a standarized uniform title or a descriptive title for a manuscript item.
For retroconversion, use the form of the title given in the source catalogue (if one is given); for new cataloguing (or if the converted catalogue does not supply a title), use a standard form from the usual reference works; if a standard form cannot be found, one should be supplied by the cataloguer. By default titles are displayed in italic font.
If the title is descriptive, the type attribute should then be set with the value desc. This will display the title in normal font. Alternative titles should be give a type of alt, and main and sub can be used if there is a subtitle.
When providing translations of the title, or multiple versions in different scripts or forms of transliteration, add them as sibling <title> elements, each with an xml:lang attribute. Do not use <foreign> except to mark up a word or phrase within a title as being in a different language to the rest of the title.
If you are not responsible for maintaining the authority files, go to the web site, click the Works button, and search to see if the same work already exists in another manuscript in the same catalogue, with the same or similar (or translated) title. If it has, set the key attribute in the <title> element(s) to the identifier of the existing record, which is the part of the URL after the last slash, starting with "work_". Otherwise, leave the key attribute blank and an identifier will be assigned to it at a later date.
Retroconversion: include these items if they are given. New cataloguing: include these items for all texts. The absence of a rubric need not be noted, although it can be included in a <note> if it is significant (e.g. all other texts do have rubrics).
Follow the principles of transcription outlined above 1.3.6. Transcription to transcribe the MS. or to encode the text given in an existing catalogue.
For mutilated items the attribute defective should be used with value true.
The <rubric>, <incipit>, etc. elements should not have final punctuation, unless they contain more than one sentence, in which case there should be a closing period.
The <incipit> elements in a catalogue may be processed to generate an alphabetical list of incipits similar to those in a print catalogue.
For long and complex incipits, care should be taken to mark up the content in a way that enables multiple index entries to be generated to aid discovery.
The physical description includes serveral different aspects of the manuscript (or part of a manuscript) including:
Provide a transcription of the words found at the beginning of the recto side of the second leaf of the manuscript. These were often used in medieval book-lists or inventories and may sometimes be useful for identification of provenance – or simply for modern-day identification.
This information is placed inside the <secFol> element, inside a <p> element, directly after <physDesc>
If the manuscript begins imperfectly – for instance, if the first leaf of text is missing – provide both the original and the present-day secundo folio, in order to avoid any ambiguity.
If the manuscript begins with prefatory paratextual matter, such as an index, you should record the secundo folio in both this and the main text. Use <locus> to record the location of each.
If the secundo folio begins mid-word, the missing portion may be provided inside a <supplied> element
The <supportDesc> element may contain the following elements:
The support material for the codicological unit(s) should be recorded in the material attribute of <supportDesc>. Allowed values are: chart (for all kinds of paper), perg (for parchment and vellum), papyrus, palm (palm leaf), mixed, unknown, or other. The name of the material for display purposes, and further description of the support, should be added in the <support> element. For example:
Note that this convention regarding H and F differs from the usage attributed to Julian Brown, in which our HFFH would be rendered HHHH, the H in the latter case describing the recto of each leaf in the first half of the quire. If retroconverting, ensure that you have understood the original intention of the cataloguer.
If different materials are used (paper and parchment, different kinds of parchment, or different paper stocks, for example), these may be described in separate <material> elements.
The level of detail in which paper is described will vary: in retroconversion, according to the detail of existing descriptions; in cataloguing afresh, according to the resources available
The paper should be described inside the <support> element. If there are multiple paper stocks, each should be described in its own <material> element.
The folding of the paper should be recorded using a <measure> element with the type attribute (value: folding) and quantity attribute whose values will be folio, quarto, etc.
The original size of the sheet may be given using <dimensions> with attribute type of value paperSheet
The number of chainlines per leaf should be recorded using a <measure> element with type of value chainlinesLeaf and an appropriate value of quantity.
The distance between chainlines may be recorded using <dimensions> with type of chainLines, containing a <width> element with quantity.
Describe each watermark in the <watermark> element.
The key term for the motif should be encoded using the <term> element with attribute type of value watermarkMotif and attribute key with the relevant value from the IPH standard. Additional descriptive terms may be placed inside a <note> element with type of watermarkVariation
The position of the watermark should be recorded in a <note> element with type of watermarkPosition
The dimensions of the watermark may be given in a <dimensions> element with type of watermark.
References to printed repertories may be given in the format specified above at Repertories. References to online repertories may be given using the <ref> element.
Countermarks should be described using the <countermark> element. Note that this customization is not currently part of the TEI P5 standard.
This should contain:
<seg> and type may be used to separate these sections within extent, as shown below.
If the present state of the item is different from its original state, record this information within <objectType>, using the following terms:
Where necessary (particularly in the case of fragments), further brief description may be provided after the closing <objectType> tag, using the following terms:
The number of leaves within a manuscript has generally been expressed using a formula that separates endleaves from the leaves at the ‘core’ of the volume (formed by gatherings of leaves whose structure can be determined in <collation>). E.g. ii + 320 + ii (i.e. a medieval manuscript opening with two post-medieval endleaves, then 320 medieval leaves, and closing with two post-medieval endleaves).
Sometimes, a formula might distinguish between different kinds of endleaf. Example: ii + 1 + 320 + ii (i.e. a medieval manuscript opening with two post-medieval endleaves, a single medieval leaf, then 320 medieval leaves, and closing with two post-medieval endleaves).
It can sometimes be difficult to distinguish whether such leaves as that denoted by ‘+ 1’ in the above formula are original (i.e. were included in the manuscript when it was first made), contemporary (i.e. included around that time), or were added at some later juncture as part of a rebinding during the medieval period. In any case, they are not part of the quire structure.
Since this kind of endleaf may contain (for example) annotations, added texts, or information of relevance to the manuscript’s medieval provenance, or may comprise leaves recycled from another medieval manuscript (and therefore bearing text in need of identification), the current guide recommends that these endleaves be distinguished both from others that were clearly added later and from the ‘core’ leaves in a volume.
Use <measure> to encode each group of leaves separately, with the attribute value to provide the number of leaves within that group.
Use the following conventions:
The terms ‘medieval’ and ‘post-medieval’ have been avoided in order that it might be possible to apply the same vocabulary and encoding practice to the task of cataloguing early modern manuscripts.
Use the tag <dimensions> to encode measurements of the leaves and the attribute type to indicate what is being measured. The following values of type may be used:
Round measurements to the nearest 5mm - except for single-sheet documents or fragments.
Use the attribute unit to specify the measurement system. Dimensions should be measured in mm. when cataloguing afresh. For retroconversion, follow whichever system the catalogue has used. Suggested values of unit:
The quantity attribute should be used to provide a machine-readable form of the measurement.
The unit of measurement (mm., etc.) should not be expressed in prose but will be generated by the XSLT transformation.
<extent> will not presently accommodate <locus>. For manuscripts that are not composite, but which nonetheless contain sections (perhaps, but not necessarily a whole quire or quires) with dimensions different to others of the volume, it is not currently possible to provide separate measurements that are distinguished by folio range. These details may be recorded in a <note>.
Measurements of the ruled and/or written spaces is often best given under <layout>. However, it is recognised that in printed catalogues, these measurements usually follow immediately on from measurements of leaf size (usually in brackets). In order to accommodate the continuation of this practice, and assist in retroconversion, the present guide accepts that it may be desirable to give measurements of ruled and/or written spaces under <extent>. Follow the practices as outlined above, using the attribute type with the values ruled or written as appropriate.
The <foliation> element is used to provide information about the systems used to number the folios or pages in the manuscript. It should record where and in what medium the numbers are written, and when this was done, and the sequence of those numbers. Where multiple systems have been used these can be referred to elsewhere if xml:id attributes are used. For example:
The <fw> element can be used to describe running heads. For example:
The collation formula should be given inside the <formula> element.
The following terminology is recommended:
| Not present | when a leaf has been removed or lost, without affecting the contents of the volume, but for reasons that cannot presently be established. |
| Excised | when a leaf has clearly been cut out deliberately (esp. if blank). |
| Missing | when a leaf has been lost, perhaps but not necessarily accidentally, causing the text or decorative scheme to become imperfect. |
| Cancelled | when a leaf has been removed but there is no evident interruption to the text or decorative scheme (e.g. leaf with an error, removed during copying). |
| Inserted | when an extra leaf is contemporary with the production of the manuscript (e.g. a miniature on a single leaf in a Book of Hours). |
| Added | when an extra leaf is a later insertion. |
Record the catchwords in the <catchwords> element.
For multi-part manuscripts, the collation of each part should be recorded at the level of the msPart; it may also be recorded at the level of the manuscript as a whole if this aids clarity. In retroconversion this is likely to involve reorganization of the formula.
The layout section (which might more fully be called ‘layout and preparation of the page’) should be used to record: written and/or ruled space (but see also under Extent); number of columns and number of written and/or ruled lines; how and according to what pattern ruling was executed; whether the writing is ‘above’ or ‘below’ top line; and evidence for pricking of the page. This section comprises one or more <layout> elements inside the <layoutDesc> element.
If desired, the <seg> element may be used to divide the content of a <layout> element, using attribute type to label the sections, suggested values ruling, pricking.
Give the number of columns and ruled lines in the <layout> element using the columns and ruledLines or writtenLines attribute. If the number of columns and/or written or ruled lines varies give the minimum and maximum values with whitespace in-between.
In most descriptions, you need only provide a count of the number of written lines. If there is a discernible difference between the number of lines ruled and the number of lines written, use both ruledLines and writtenLines in order to differentiate.
There is as yet no straightforward means of recording the varying dimensions of columns and intercolumnar margins for the more complex, multi-column layouts such as those found in glossed books. Give a prose description instead.
Record the written (and/or ruled) space in the <dimensions> element with type of written/ruled as appropriate.
The description of the ruling type may be according to: a printed repertory (use the standard markup for repertoria); a verbal description; the formula established by D. Muzerelle, De re rigatoria [http://www.palaeographia.org/muzerelle/index.htm]. In the latter case the formula should be enclosed in a <formula> element with attribute notation of value Muzerelle
If the layout varies between different sections of the manuscript, use separate <layout> elements to record this.
Complex or unusual layouts may be encoded using the type and subtype attributes on <layout>. (Note that this customization is not currently part of the TEI P5 standard.) For example:
The type and subtype attributes should be used to encode the layout of fragments if the written area of a page is not fully preserved.
To encode the existing form of a fragment, use type with fragment
For processing purposes this encoding should be interpreted as, respectively: at least one column, at least 12 lines; at least one column, 55 lines; two columns, at least 46 lines.
Each distinct hand and/or script in the codicological unit should be described in a separate <handNote> element in the <handDesc> element. The <handDesc> element itself has an attribute hands which can be used to record the number of hands identified. This is optional but recommended. The value of the attribute should be the number of hands involved in the original production of the manuscripts and should not include later additions or annotations.
The <handNote> element may have an xml:id attribute with the values hand-1, hand-2 etc, numbered in the order of appearance in the manuscript. If the same hand occurs in another unit the attribute sameAs may be used with a reference to the xml:id of that <handNote>.
The folios where the hand occurs should be specified and may be encoded using the <locus> or <locusGrp> element. Where the scribe is identifiable, either from the writing or a subscription, give the name in a <persName> element using the key attribute pointing to the persons authority file, and the role attribute with value scr.
The scope attribute can be used to indicate the extent of the hand's appearance in the manuscript. Its values can be one of:
The script attribute may be used to provide a high-level classification of the script. Suggested values in Western manuscripts are:
The classification for early scripts is based on Brown (1990) with modifications, for Gothic scripts on Derolez (2003), for humanistic scripts on Derolez (2011).
The attribute execution can be used to describe the formality of the script's execution, according to the classifications developed by Lieftinck, Gumbert, and Derolez. Note that this customization is not currently part of the TEI P5 standard.
In Islamicate manuscripts suggested script values are:
The <decoDesc> element contains a description of the decoration in the manuscript or codicological unit, together with other ‘decorative’ aspects of the presentation of the text such as rubrication, It can only contain the elements <p>, <summary>, and <decoNote>.
Within the tag <decoDesc>, use <decoNote> to provide a hierarchical breakdown of the decoration in the manuscript, in the order given in the following table, with the appropriate values of type attribute.
| Miniatures (or coloured drawings), listed in the following order: full-page, half-page, small, column; use for painted or tinted images, whether part of an original decorative scheme or added. | miniature |
| Uncoloured drawings or sketches, whether part of an original decorative scheme or added. | drawing |
| Bas-de-page scenes | bas-de-page |
| Borders, in the following order: historiated, other; use for painted borders of any type (including for example historiated, inhabited, foliate) | border |
| Diagram | diagram |
| Map | map |
| Headpiece | headpiece |
| Canon table | canonTable |
| Carpet page | carpetPage |
| Historiated initials (i.e., containing an identifiable narrative scene) (Brown: historiated initial); initials, usually painted, containing identifiable persons or narrative scenes usually related to the text. | histInit |
| decorated initials (Brown: decorated initial, anthropomorphic initial, zoomorphoric initial, gymnastic initial, inhabited initial). Other initials with significant decorative features, usually painted; includes 'arabesque' and 'silhouette' initials. | decInit |
| coloured initials (i.e. of a single colour with no or minimal decorative features) | colInit |
| initials with penwork flourishing (Reallexikon zur Deutschen Kunstgeschichte: fleuronné) (Brown: pen-flourished initial, littera florissa). Initials with "fine linear embellishment" (Brown) often in a contrasting colour (includes 'puzzle' initials); borders of similar embellishment. | flourInit |
| chrysography (i.e. writing in gold) | chrysography |
| plain initials (i.e. in the ink of the text and with no or minimal decorative features) | plainInit |
| Line fillers | lineFill |
| cadels | cadel |
| instructions | instructions |
| Spaces left for decoration | unfilled |
| None (if an existing decoration being retro-converted specifies this) | none |
| rubrication | rubrication |
In Fihrist, the following values for the type attribute should be used:
Artists should be identified using the <persName> element with role = art and key referring to the persons authority file.
To provide a more structured entry in the case of detailed descriptions of decoration, use the <list>, <head>, and <item> elements.
Aspects of the manuscript relating to the presentation of the text - notably rubrication - should also be included in the <decoDesc> element (rather than in the <layout> element, using <decoNote> with attribute type of value rubrication.
Marginalia, notes, and other additions of interest should usually be recorded in the <additions> element, inside one or more <p> or <note> elements. The <note> element can have the type and subtype attributes. Use <locus> to specify the location of these features.
If the language of the marginalia is significant (e.g., Latin marginalia in a Greek manuscript), the marginalia will need to be recorded as an additional text using <msItem> in <msContents>.
The binding should be described in one or more paragraphs (<p>) in a <binding> element inside the <bindingDesc> element. The standard dating attributes should be used on the <binding> element if information about the date of the binding is available.
The following order may be followed in the description:
Key elements of the description may be marked with the <term> with relevant type attribute and with attribute ref referring to the appropriate URI in the Ligatus thesaurus.
Give the height, width and depth of the binding may be given in mm (with 5 mm precision) in the <dimensions> element (type attribute with value binding).
A description of decorative features on the binding can be recorded in one or more <decoNote> elements (note that this needs to be outside the <p> element as a child of <binding>)
Use the <condition> element to record repairs to the binding, such as rebacking.
Fore-edge painting or decoration should be described inside a <decoDesc> element, in a <decoNote> element with attribute type of value foreedge.
Bookmarks and other page markers should be described in a separate paragraph in the binding section, using where possible the vocabulary of the Ligatus thesaurus, and linking to that vocabulary using the <term> element with attribute type of value bookmark and relevant ref attribute.
Evidence of former bindings, or the reuse of earlier binding material in a modern binding, should be recorded in a separate <binding> element.
Note that all the above may require restructuring of an original description during retroconversion.
The <sealDesc> element supplies information about the seals attached to documents. It can either contain a text description in <p> tags, or any number of <seal> elements. These can be numbered using n attributes.
The seal impression of stamps of ownership may be described in <decoDesc>, in stylistic and decorative terms, or in <provenance> as regards its textual content.
The <accMat> element may be used for brief descpritions of endleaves, waste leaves and similar material that are not part of the ‘original’ codex but were supplied during a binding process. If a detailed codicological description is required, use <msPart>
Use <p> to split up descriptions of multiple materials, and <locus> to identifying their locations.
The <history> element should include information about the origin, provenance and acquisition of the manuscript.
In the <origin> element specify date (<origDate>) and place (<origPlace>) (if known) of the manuscript's production. If not known, state this in a <p> element. Do not enclose a statement such as "No date" or "n.d." with <origDate> tags.
Dating attributes from the set notBefore, notAfter, from, to and when MUST be used for <origDate>
from and to denote a known period of writing, presumed to be more or less continuous, beginning at one date and ending at another. notBefore and notAfter denote the terminus a quo and terminus ad quem within which the writing is believed to have occured.
The values of those attributes are a date, starting with the year, then the month, then the day, separated by hyphens (but most often just a year, always expressed using four-digits) must be in the Gregorian calendar. the calendar attribute records the calendar system used by the expression of the date in the text enclosed by the <origDate> tags. The text is for display, the attributes are the machine-readable interpretation. For example:
In retroconversion, the values given to the element and its attributes should reflect the conventions of the particular catalogue as expressed in the catalogue or, if necessary, as inferred by the encoder. (If inferred, a note to this effect may be added in <encodingDesc>.)
Values used in the Bodleian medieval catalogue (intended to capture the usage of the Summary Catalogue and Paecht and Alexander) are as follows:
| Early 14th century | 1300-1310 |
| Mid 14th century | 1340-1360 |
| Late 14th century | 1390-1400 |
| 14th century, first quarter | 1300-1325 |
Etc.
Values of dating attributes should be inclusive, i.e. 1000-1050, not 1001-1050 or 1000-1049.
The attribute evidence MAY be used to indicate the evidence for dating and localization. It is assumed that this will usually be equivalent to conjecture. If there is reasonable certainty about the dating or localization (the manuscript is 'dated or datable') this SHOULD be indicated using the attribute cert with value high, and the nature of the evidence may be specified with the evidence attribute.
For manuscripts with significant later additions, textual or decorative, use additional <origDate> elements with type of additions
The content of <origPlace> should where possible be structured in the order (where relevant), country, settlement, institution. These should be marked up using the <country>, <settlement>, and <org> elements, which MUST have attributes key linking to the places authority file. Or, in catalogues such as Fihrist which have a subjects authority file instead of a places one, the key attribute should be "subject_" followed by the Library of Congress Name Authority identifier (e.g. "subject_n12345678").
There MUST be a country or country-like entity (see below), inside a <country> tag, if the <origPlace> element is used.
In Western manuscripts, countries of origin are typically expressed with reference to modern countries with some exceptions. Examples: England, France, Spain, Italy, Germany, Austria, Switzerland, but Bohemia, Dalmatia, Serbia, Flanders.
Record the different stages in the provenance in one or more <provenance> elements.
There are different conventions for the presentation of provenance evidence. Recommended best practice in these guidelines (which may involve some restructuring of material in the case of retroconversion) is that where possible each provenance event should occur in its own <provenance> element, which should have relevant dating attributes (when, notBefore, etc.). (They may alternatively contain <date> elements with those attributes.) As elsewhere, from and to denote a known period, presumed to be more or less continuous, beginning at one date and ending at another. notBefore and notAfter denote the terminus a quo and terminus ad quem within which the writing is believed to have occured. when denotes a single event (such as a dated signature or the donation of an item to a library). People involved in the transfer of ownership should be marked up with <persName> tags, with a role attribute (a Library of Congress relator code, usually "fmo" for former owner).
The <acquisition> element should describe the last stage of the manuscript's history, i.e. how it was acquired by its present owners. It SHOULD have relevant dating attributes. Because the present owner, locaton etc. of the manuscript are recorded elsewhere in the manuscript description, it is NOT necessary to encode them using <orgName> or <persName> elements.
Note the usage of the different dating attributes in the following example.
The <acquisition> element is also the place to record any funding bodies which contributed to the cost of purchasing the manuscript. Each should be tagged as <orgName> elements with a role attribute of either "spn" or "fnd". The websites of sponsors, and their logos, can be included. For example:
Ideally the @url attribute of the <graphic> element should point to an image hosted by the funding organization. The <graphic> element cannot be a child of the <funder> element, but must be enclosed in a <persName> or <orgName> element.
Contributions to the cost of cataloguing the manuscript should be recorded in the Title Statement.
The <additional> element is used to provide: information about the source of the description; information about the availability and custodial history of the manuscript; information about surrogates; bibliography; and links to online resources.
The <source> element, contained in <recordHist>, provides a prose description of the source(s) from which the description has been derived; this information will overlap with the information in <respStmt>. It may contain <listBibl> and <bibl> elements.
The <availability> element can be used to supply information about the availability of a manuscript, using the status attribute. Valid values for status are free, unknown, restricted, offsite, exhibition, printcat, none. It may also contain information about the images or text, such as any restrictions on their use or distribution, their copyright status, etc.
The <custodialHist> element can be used to describe a manuscript's custodial history (e.g. conservation, exhibitions) either as prose tagged with <p> elements, or as a series of custodial events, using the <custEvent> element with attributes type, when, etc.
The <custEvent> element is currently used at the Bodleian to record barcoding of manuscripts:
The <surrogates> element, which follows <recordHist>, is used to link to digital or other facsimiles where these are hosted independently from the catalogue. The structure of a typical entry is shown below. The subtype attribute on the <bibl> element has the values full, where a manuscript has been digitized in full, or partial, where only selected items are available.
This section should also be used to record the availability of microfilms.
The bibliography of works referring to the manuscript should be recorded in the <additional> element in a <listBibl> element. In the Bodleian medieval catalogue only major printed descriptions or reproductions of the manuscript are listed here; other items should be recorded in the Zotero bibliography. The works should be listed in a chronological order, with the most recent item first.
This section is also used to provide links to online resources such as Pinakes, Trismegistos, JONAS etc. Online resources are placed in a separate <listBibl> element with the heading <head> 'Online resources:'.
For multi-part manuscripts or in other cases where a ‘syntactical’ description (Andrist et al., 2013) is required, the <msPart> element should be used. These guidelines recommend the use of <msPart> for:
The definition and understanding of composite manuscripts varies between different codicological traditions. The Western tradition has typically understood a composite manuscript to be composed of more than one combined production/usage unit. (For this terminology see Kwakkel 2002). Manuscripts with separate-but-contemporaneous production units, that were not also at some point separate usage units, are not typically catalogued as composite, although the different production units are usually noted in the description. (For a recent example, see Hanna and Rundle, Cat. Christ Church MSS., MS. 92.)
The use of <msPart> is not recommended for describing added text or decoration where this has been added on the original codicological unit as a supplement to existing text (rather than, as with a palimpsest, as a replacement for that text). In those cases, use of multiple <origDate> and/or <origPlace> elements is recommended; see above.
For composite manuscripts, each codicological unit should be described in a separate <msPart> element using the following elements:
Endleaves should be described using one or more <msPart> elements following the <msDesc> element which contains the description of the main manuscript.
The element <msFrag> should not be used for this purpose. This element is used for describing manuscripts that have been 'virtually reconstructed' and is not currently used in this project.
Example: MS. Auct. D. 2. 14 (abbreviated)
Example: MS. Holkham Gr. 15 (simplified)
Divide the contents: Calendar; Suffrages (each saint listed as a separate <msItem>); Hours of the Virgin; Hours of the Passion; and so on – and then, using decimal point numbering for <msItem>, subdivide each of the Hours into the canonical hours, where present (Matins, Lauds, Prime, and so on).
Divide the contents: Prologue to the Vulgate; Old Testament; New Testament; ‘Interpretationes nominum hebraicorum’; and so on - and then, using decimal point numbering for <msItem>, subdivide each one where appropriate, distinguishing between the biblical text and their prologues.
| <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text] | |||||||||
| Module | textstructure — Schema | ||||||||
| Attributes |
| ||||||||
| Contained by | textstructure: TEI | ||||||||
| May contain | |||||||||
| Note | This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. | ||||||||
| Example | <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>The shortest TEI Document Imaginable</title>
</titleStmt>
<publicationStmt>
<p>First published as part of TEI P2, this is the P5
version using a namespace.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<body>
<p>This is about the shortest TEI document imaginable.</p>
</body>
</text>
</TEI> | ||||||||
| Example | <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>A TEI Document containing four page images </title>
</titleStmt>
<publicationStmt>
<p>Unpublished demonstration file.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<facsimile>
<graphic url="page1.png"/>
<graphic url="page2.png"/>
<graphic url="page3.png"/>
<graphic url="page4.png"/>
</facsimile>
</TEI> | ||||||||
| Schematron |
<sch:rule context="tei:TEI">
<sch:assert test="matches(@xml:id, '^manuscript_\d+$') or contains(base-uri(.), 'genizah-mss')"
role="fatal"> The root TEI element must have an @xml:id
beginning with "manuscript_" then a number (which must also
be unique across the entire catalogue). </sch:assert>
<sch:assert test="matches(@xml:id, '^volume_\d+$') or not(contains(base-uri(.), 'genizah-mss'))"
role="fatal"> The root TEI element must have an @xml:id
beginning with "volume_" then a number (which must also be
unique across the entire catalogue). </sch:assert>
</sch:rule> | ||||||||
| Schematron |
<sch:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<sch:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/> | ||||||||
| Schematron |
<sch:ns prefix="rng"
uri="http://relaxng.org/ns/structure/1.0"/>
<sch:ns prefix="rna"
uri="http://relaxng.org/ns/compatibility/annotations/1.0"/> | ||||||||
| Schematron |
<sch:ns prefix="sch"
uri="http://purl.oclc.org/dsdl/schematron"/>
<sch:ns prefix="sch1x"
uri="http://www.ascc.net/xml/schematron"/> | ||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="teiHeader"/>
<alternate minOccurs="1" maxOccurs="1">
<sequence minOccurs="1" maxOccurs="1">
<classRef key="model.resource"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="TEI" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<elementRef key="TEI" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element TEI
{
att.global.attributes,
att.typed.attributes,
attribute version { text }?,
( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}⚓ | ||||||||
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions] | |||||||||||||
| Module | core — Schema | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||
| Note | If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>. | ||||||||||||
| Example | <choice>
<expan>North Atlantic Treaty Organization</expan>
<abbr cert="low">NorATO</abbr>
<abbr cert="high">NATO</abbr>
<abbr cert="high" xml:lang="fr">OTAN</abbr>
</choice> | ||||||||||||
| Example | <choice>
<abbr>SPQR</abbr>
<expan>senatus populusque romanorum</expan>
</choice> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element abbr
{
att.global.attributes,
att.typed.attribute.subtype,
attribute type { text }?,
macro.phraseSeq
}⚓ | ||||||||||||
| <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <accMat>A copy of a tax form from 1947 is included in the envelope
with the letter. It is not catalogued separately.</accMat> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element accMat
{
att.global.attributes,
att.typed.attributes,
macro.specialPara
}⚓ |
| <acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: history | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <acquisition>Left to the <name type="place">Bodleian</name> by
<name type="person">Richard Rawlinson</name> in 1755.
</acquisition> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element acquisition
{
att.global.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.specialPara
}⚓ | ||||||||||
| <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended. In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project. |
| Example | The story I am
going to relate is true as to its main facts, and as to the
consequences <add place="above">of these facts</add> from which
this tale takes its title. |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element add
{
att.global.attributes,
att.transcriptional.attributes,
att.placement.attributes,
att.typed.attributes,
att.dimensions.attributes,
macro.paraContent
}⚓ |
| <additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | |
| May contain | msdescription: adminInfo surrogates |
| Example | <additional>
<adminInfo>
<recordHist>
<p>
<!-- record history here -->
</p>
</recordHist>
<custodialHist>
<p>
<!-- custodial history here -->
</p>
</custodialHist>
</adminInfo>
<surrogates>
<p>
<!-- information about surrogates here -->
</p>
</surrogates>
<listBibl>
<bibl>
<!-- ... -->
</bibl>
<!-- full bibliography here -->
</listBibl>
</additional> |
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="adminInfo"
minOccurs="0"/>
<elementRef key="surrogates"
minOccurs="0"/>
<elementRef key="listBibl" minOccurs="0"/>
</sequence>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element additional
{
att.global.attributes,
( ( adminInfo?, surrogates?, listBibl? ) | model.pLike+ )
}⚓ |
| <additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <additions>
<p>There are several marginalia in this manuscript. Some consist of
single characters and others are figurative. On 8v is to be found a drawing of
a mans head wearing a hat. At times sentences occurs: On 5v:
<q xml:lang="is">Her er skrif andres isslendin</q>,
on 19r: <q xml:lang="is">þeim go</q>,
on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
batar þad mælgi ok mal</q>,
On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
</additions> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element additions { att.global.attributes, macro.specialPara }⚓ |
| <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: address |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text. |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL</addrLine>
<addrLine>60680 USA</addrLine>
</address> |
| Example | <addrLine>
<ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element addrLine { att.global.attributes, macro.phraseSeq }⚓ |
| <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal publicationStmt scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Note | This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc. |
| Example | Using just the elements defined by the core module, an address could be represented as follows: <address>
<street>via Marsala 24</street>
<postCode>40126</postCode>
<name>Bologna</name>
<name>Italy</name>
</address> |
| Example | When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>: <address>
<street>via Marsala 24</street>
<postCode>40126</postCode>
<settlement>Bologna</settlement>
<country>Italy</country>
</address> |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL 60680</addrLine>
<addrLine>USA</addrLine>
</address> |
| Example | <address>
<country key="FR"/>
<settlement type="city">Lyon</settlement>
<postCode>69002</postCode>
<district type="arrondissement">IIème</district>
<district type="quartier">Perrache</district>
<street>
<num>30</num>, Cours de Verdun</street>
</address> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.addrPart"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element address
{
att.global.attributes,
( model.global*, ( model.addrPart, model.global* )+ )
}⚓ |
| <adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: additional |
| May contain | |
| Example | <adminInfo>
<recordHist>
<source>Record created <date>1 Aug 2004</date>
</source>
</recordHist>
<availability>
<p>Until 2015 permission to photocopy some materials from this
collection has been limited at the request of the donor. Please ask repository staff for details
if you are interested in obtaining photocopies from Series 1:
Correspondence.</p>
</availability>
<custodialHist>
<p>Collection donated to the Manuscript Library by the Estate of
Edgar Holden in 1993. Donor number: 1993-034.</p>
</custodialHist>
</adminInfo> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="recordHist"
minOccurs="0"/>
<elementRef key="availability"
minOccurs="0"/>
<elementRef key="custodialHist"
minOccurs="0"/>
<classRef key="model.noteLike"
minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element adminInfo
{
att.global.attributes,
( recordHist?, availability?, custodialHist?, model.noteLike? )
}⚓ |
| <altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: msFrag msIdentifier | ||||||||||
| May contain | |||||||||||
| Note | An identifying number of some kind must be supplied if known; if it is not known, this should be stated. | ||||||||||
| Example | <altIdentifier>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>MS.El.26.C.9</idno>
</altIdentifier> | ||||||||||
| Content model |
<content>
<sequence>
<classRef key="model.placeNamePart"
expand="sequenceOptional"/>
<elementRef key="institution"
minOccurs="0"/>
<elementRef key="repository"
minOccurs="0"/>
<elementRef key="collection"
minOccurs="0"/>
<elementRef key="idno"/>
<elementRef key="note" minOccurs="0"/>
</sequence>
</content>
⚓ | ||||||||||
| Schema Declaration |
element altIdentifier
{
att.global.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
(
placeName?,
country?,
region?,
settlement?,
district?,
geogName?,
institution?,
repository?,
collection?,
idno,
note?
)
}⚓ | ||||||||||
| <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Example | do you <abbr>Mr<am>.</am>
</abbr> Jones?
|
| Example | <choice>
<abbr>Aug<am>g</am>
</abbr>
<expan>Aug<ex>ustorum duo</ex>
</expan>
</choice> |
| Example | <abbr>eu<am>
<g ref="#b-er"/>
</am>y</abbr>
<abbr>
<am>
<g ref="#b-per"/>
</am>sone
</abbr> ...
|
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.pPart.transcriptional"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element am
{
att.global.attributes,
att.typed.attributes,
att.editLike.attributes,
( text | model.gLike | model.pPart.transcriptional )*
}⚓ |
| <analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core — Schema |
| Attributes |
|
| Contained by | core: biblStruct |
| May contain | |
| Note | May contain titles and statements of responsibility (author, editor, or other), in any order. The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item. |
| Example | <biblStruct>
<analytic>
<author>Chesnutt, David</author>
<title>Historical Editions in the States</title>
</analytic>
<monogr>
<title level="j">Computers and the Humanities</title>
<imprint>
<date when="1991-12">(December, 1991):</date>
</imprint>
<biblScope>25.6</biblScope>
<biblScope>377–380</biblScope>
</monogr>
</biblStruct> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="respStmt"/>
<elementRef key="title"/>
<classRef key="model.ptrLike"/>
<elementRef key="date"/>
<elementRef key="textLang"/>
<elementRef key="idno"/>
<elementRef key="availability"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element analytic
{
att.global.attributes,
(
author
| editor
| respStmt
| title
| model.ptrLike
| date
| textLang
| idno
| availability
)*
}⚓ |
| <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |||||||||||
| Module | core — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource. In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast. Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given. | ||||||||||
| Example | <author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
<persName>Beaumont, Francis</persName> and
<persName>John Fletcher</persName>
</author>
<author>
<orgName key="BBC">British Broadcasting
Corporation</orgName>: Radio 3 Network
</author> | ||||||||||
| Schematron |
<sch:rule context="//tei:msItem//tei:author[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'person_\d+')]">In the
medieval catalogue, the author element, when a child of
msItem, must have a key matching the pattern
'person_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element author
{
att.global.attributes,
att.naming.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: monogr header: publicationStmt |
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <authority>John Smith</authority> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element authority
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq.limited
}⚓ |
| <availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.] | |||||||||
| Module | header — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | A consistent format should be adopted | ||||||||
| Example | <availability status="restricted">
<p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
<p>In the public domain</p>
</availability>
<availability status="restricted">
<p>Available under licence from the publishers.</p>
</availability> | ||||||||
| Example | <availability>
<licence target="http://opensource.org/licenses/MIT">
<p>The MIT License
applies to this document.</p>
<p>Copyright (C) 2011 by The University of Victoria</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.</p>
</licence>
</availability> | ||||||||
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.availabilityPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element availability
{
att.global.attributes,
att.declarable.attributes,
attribute status
{
list
{
(
"free"
| "restricted"
| "exhibition"
| "offsite"
| "printcat"
| "none"
| "unknown"
)+
}
}?,
( model.availabilityPart | model.pLike )+
}⚓ | ||||||||
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |||||||||||
| Module | core — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: add bibl cit corr del desc head hi item l listBibl note orig p q quote ref reg relatedItem sic textLang title unclear header: change handNote licence scriptNote sourceDesc taxonomy linking: seg | ||||||||||
| May contain | core: abbr add address author bibl biblScope choice citedRange corr date del editor email expan foreign gap hi lb measure name note num orig pb ptr pubPlace publisher q ref reg relatedItem respStmt series sic term textLang title unclear figures: figure gaiji: g linking: seg namesdates: addName country district forename geo geogFeat geogName listRelation orgName persName placeName region settlement surname character data | ||||||||||
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class | ||||||||||
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl> | ||||||||||
| Example | <bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>.
</bibl> | ||||||||||
| Example | <bibl type="article" subtype="book_chapter"
xml:id="carlin_2003">
<author>
<name>
<surname>Carlin</surname>
(<forename>Claire</forename>)</name>
</author>,
<title level="a">The Staging of Impotence : France’s last
congrès</title> dans
<bibl type="monogr">
<title level="m">Theatrum mundi : studies in honor of Ronald W.
Tobin</title>, éd.
<editor>
<name>
<forename>Claire</forename>
<surname>Carlin</surname>
</name>
</editor> et
<editor>
<name>
<forename>Kathleen</forename>
<surname>Wine</surname>
</name>
</editor>,
<pubPlace>Charlottesville, Va.</pubPlace>,
<publisher>Rookwood Press</publisher>,
<date when="2003">2003</date>.
</bibl>
</bibl> | ||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.highlighted"/>
<classRef key="model.pPart.data"/>
<classRef key="model.pPart.edit"/>
<classRef key="model.segLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.biblPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ | ||||||||||
| Schema Declaration |
element bibl
{
att.global.attributes,
att.declarable.attributes,
att.typed.attribute.subtype,
att.sortable.attributes,
att.docStatus.attributes,
attribute type
{
"MS"
| "QUARTO"
| "SC"
| "OC"
| "bible"
| "commentary"
| "edition"
| "extract"
| "related"
| "text-relations"
| "translation"
}?,
(
text
| model.gLike
| model.highlighted
| model.pPart.data
| model.pPart.edit
| model.segLike
| model.ptrLike
| model.biblPart
| model.global
)*
}⚓ | ||||||||||
| <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint. |
| Example | <biblScope>pp 12–34</biblScope>
<biblScope unit="page" from="12" to="34"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element biblScope
{
att.global.attributes,
att.citing.attributes,
macro.phraseSeq
}⚓ |
| <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: add cit corr del desc head hi item l listBibl note orig p q quote ref reg relatedItem sic textLang title unclear header: change handNote licence scriptNote sourceDesc taxonomy linking: seg |
| May contain | core: analytic citedRange monogr note ptr ref relatedItem series |
| Example | <biblStruct>
<monogr>
<author>Blain, Virginia</author>
<author>Clements, Patricia</author>
<author>Grundy, Isobel</author>
<title>The Feminist Companion to Literature in English: women writers from the middle ages
to the present</title>
<edition>first edition</edition>
<imprint>
<publisher>Yale University Press</publisher>
<pubPlace>New Haven and London</pubPlace>
<date>1990</date>
</imprint>
</monogr>
</biblStruct> |
| Example | <biblStruct type="newspaper">
<analytic>
<author>
<forename>David</forename>
<surname>Barstow</surname>
</author>
<author>
<forename>Susanne</forename>
<surname>Craig</surname>
</author>
<author>
<forename>Russ</forename>
<surname>Buettner</surname>
</author>
<title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
<title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
</analytic>
<monogr>
<title level="j">The New York Times</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>A. G. Sulzberger</publisher>
<date when="2018-10-03">Wednesday, October 3, 2018</date>
</imprint>
<biblScope unit="volume">CLXVIII</biblScope>
<biblScope unit="issue">58,104</biblScope>
<biblScope unit="page">1</biblScope>
</monogr>
</biblStruct> |
| Content model |
<content>
<sequence>
<elementRef key="analytic" minOccurs="0"
maxOccurs="unbounded"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="monogr"/>
<elementRef key="series" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.noteLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="relatedItem"/>
<elementRef key="citedRange"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element biblStruct
{
att.global.attributes,
att.declarable.attributes,
att.typed.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
analytic*,
( monogr, series* )+,
( model.noteLike | model.ptrLike | relatedItem | citedRange )*
)
}⚓ |
| <binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions] | |||||||||||||||||||
| Module | msdescription — Schema | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Contained by | msdescription: bindingDesc | ||||||||||||||||||
| May contain | |||||||||||||||||||
| Example | <binding contemporary="true">
<p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp
closing to the back cover.</p>
</binding> | ||||||||||||||||||
| Example | <bindingDesc>
<binding contemporary="false">
<p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front
pastedown.</p>
</binding>
<binding contemporary="false">
<p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>
</binding>
</bindingDesc> | ||||||||||||||||||
| Schematron |
<sch:rule context="//tei:binding">
<sch:assert test="@when or @notBefore or @notAfter or @contemporary='true'"
role="warn"> The binding element should have dating
attributes (when or notBefore/notAfter) or a contemporary
attribute (with the value 'true'). </sch:assert>
</sch:rule> | ||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||||||||||
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<elementRef key="condition"/>
<elementRef key="decoNote"/>
</alternate>
</content>
⚓ | ||||||||||||||||||
| Schema Declaration |
element binding
{
att.global.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
attribute contemporary { text }?,
( model.pLike | condition | decoNote )+
}⚓ | ||||||||||||||||||
| <bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <bindingDesc>
<p>Sewing not visible; tightly rebound over
19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with
gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
cover inlaid with a 17th-cent. oval medallion of red morocco tooled in
gilt (perhaps replacing the identifying mark of a previous owner); the
spine similarly tooled, without raised bands or title-piece; coloured
endbands; the edges of the leaves and boards gilt.Boxed.</p>
</bindingDesc> |
| Content model |
<content>
<alternate>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<elementRef key="decoNote"/>
<elementRef key="condition"/>
</alternate>
<elementRef key="binding" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element bindingDesc
{
att.global.attributes,
( ( model.pLike | decoNote | condition )+ | binding+ )
}⚓ |
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure — Schema |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Example | <body>
<l>Nu scylun hergan hefaenricaes uard</l>
<l>metudæs maecti end his modgidanc</l>
<l>uerc uuldurfadur sue he uundra gihuaes</l>
<l>eci dryctin or astelidæ</l>
<l>he aerist scop aelda barnum</l>
<l>heben til hrofe haleg scepen.</l>
<l>tha middungeard moncynnæs uard</l>
<l>eci dryctin æfter tiadæ</l>
<l>firum foldu frea allmectig</l>
<trailer>primo cantauit Cædmon istud carmen.</trailer>
</body> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<classRef key="model.divTop"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divTop"/>
</alternate>
</sequence>
<sequence minOccurs="0">
<classRef key="model.divGenLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1" maxOccurs="1">
<elementRef key="schemaSpec"/>
<classRef key="model.common"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0">
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
</alternate>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element body
{
att.global.attributes,
att.declaring.attributes,
(
model.global*,
( model.divTop, ( model.global | model.divTop )* )?,
( model.divGenLike, ( model.global | model.divGenLike )* )?,
(
( model.divLike, ( model.global | model.divGenLike )* )+
| ( model.div1Like, ( model.global | model.divGenLike )* )+
| (
( ( schemaSpec | model.common ), model.global* )+,
(
( model.divLike, ( model.global | model.divGenLike )* )+
| ( model.div1Like, ( model.global | model.divGenLike )* )+
)?
)
),
( model.divBottom, model.global* )*
)
}⚓ |
| <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: category |
| May contain | header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <catDesc>Prose reportage</catDesc> |
| Example | <catDesc>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc>
</catDesc> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.catDescPart"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element catDesc
{
att.global.attributes,
att.canonical.attributes,
( text | model.limitedPhrase | model.catDescPart )*
}⚓ |
| <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | |
| May contain | |
| Example | <category xml:id="b1">
<catDesc>Prose reportage</catDesc>
</category> |
| Example | <category xml:id="b2">
<catDesc>Prose </catDesc>
<category xml:id="b11">
<catDesc>journalism</catDesc>
</category>
<category xml:id="b12">
<catDesc>fiction</catDesc>
</category>
</category> |
| Example | <category xml:id="LIT">
<catDesc xml:lang="pl">literatura piękna</catDesc>
<catDesc xml:lang="en">fiction</catDesc>
<category xml:id="LPROSE">
<catDesc xml:lang="pl">proza</catDesc>
<catDesc xml:lang="en">prose</catDesc>
</category>
<category xml:id="LPOETRY">
<catDesc xml:lang="pl">poezja</catDesc>
<catDesc xml:lang="en">poetry</catDesc>
</category>
<category xml:id="LDRAMA">
<catDesc xml:lang="pl">dramat</catDesc>
<catDesc xml:lang="en">drama</catDesc>
</category>
</category> |
| Content model |
<content>
<sequence>
<alternate>
<elementRef key="catDesc" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.descLike"/>
<elementRef key="equiv"/>
<elementRef key="gloss"/>
</alternate>
</alternate>
<elementRef key="category" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element category
{
att.global.attributes,
att.datcat.attributes,
( ( catDesc+ | ( model.descLike | equiv | gloss )* ), category* )
}⚓ |
| <cell> (cell) contains one cell of a table. [14.1.1. TEI Tables] | |
| Module | figures — Schema |
| Attributes |
|
| Contained by | figures: row |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <row>
<cell role="label">General conduct</cell>
<cell role="data">Not satisfactory, on account of his great unpunctuality
and inattention to duties</cell>
</row> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element cell
{
att.global.attributes,
att.tableDecoration.attributes,
macro.specialPara
}⚓ |
| <change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions] | |||||||||||||||||
| Module | header — Schema | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Contained by | header: revisionDesc msdescription: recordHist | ||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||
| Note | The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it. It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented. | ||||||||||||||||
| Example | <titleStmt>
<title> ... </title>
<editor xml:id="LDB">Lou Burnard</editor>
<respStmt xml:id="BZ">
<resp>copy editing</resp>
<name>Brett Zamir</name>
</respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
<change who="#BZ" when="2008-02-02"
status="public">Finished chapter 23</change>
<change who="#BZ" when="2008-01-02"
status="draft">Finished chapter 2</change>
<change n="P2.2" when="1991-12-21"
who="#LDB">Added examples to section 3</change>
<change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc> | ||||||||||||||||
| Example | <profileDesc>
<creation>
<listChange>
<change xml:id="DRAFT1">First draft in pencil</change>
<change xml:id="DRAFT2"
notBefore="1880-12-09">First revision, mostly
using green ink</change>
<change xml:id="DRAFT3"
notBefore="1881-02-13">Final corrections as
supplied to printer.</change>
</listChange>
</creation>
</profileDesc> | ||||||||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element change
{
att.ascribed.attributes,
att.datable.attributes,
att.docStatus.attributes,
att.global.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
attribute target { list { + } }?,
macro.specialPara
}⚓ | ||||||||||||||||
| <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Example | <charDecl>
<char xml:id="aENL">
<unicodeProp name="Name"
value="LATIN LETTER ENLARGED SMALL A"/>
<mapping type="standard">a</mapping>
</char>
</charDecl> |
| Content model |
<content>
<sequence>
<elementRef key="desc" minOccurs="0"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="char"/>
<elementRef key="glyph"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) }⚓ |
| <choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Note | Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel. Note also that <choice> elements may self-nest. Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred. |
| Example | An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows. <p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
<sic>1724</sic>
<corr>1728</corr>
</choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
<orig>favour</orig>
<reg>favor</reg>
</choice>.</p> |
| Content model |
<content>
<alternate minOccurs="2"
maxOccurs="unbounded">
<classRef key="model.choicePart"/>
<elementRef key="choice"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element choice { att.global.attributes, ( model.choicePart | choice )+ }⚓ |
| <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author biblScope cit citedRange corr del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material msItem musicNotation objectType origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Example | <cit>
<quote>and the breath of the whale is frequently attended with such an insupportable smell,
as to bring on disorder of the brain.</quote>
<bibl>Ulloa's South America</bibl>
</cit> |
| Example | <entry>
<form>
<orth>horrifier</orth>
</form>
<cit type="translation" xml:lang="en">
<quote>to horrify</quote>
</cit>
<cit type="example">
<quote>elle était horrifiée par la dépense</quote>
<cit type="translation" xml:lang="en">
<quote>she was horrified at the expense.</quote>
</cit>
</cit>
</entry> |
| Example | <cit type="example">
<quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
<media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
mimeType="audio/wav"/>
<cit type="translation">
<quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
</cit>
<cit type="translation">
<quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
</cit>
</cit> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.biblLike"/>
<classRef key="model.egLike"/>
<classRef key="model.entryPart"/>
<classRef key="model.global"/>
<classRef key="model.graphicLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.attributable"/>
<elementRef key="pc"/>
<elementRef key="q"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element cit
{
att.global.attributes,
att.typed.attributes,
(
model.biblLike
| model.egLike
| model.entryPart
| model.global
| model.graphicLike
| model.ptrLike
| model.attributable
| pc
| q
)+
}⚓ |
| <citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: bibl biblStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded |
| Example | <citedRange>pp 12–13</citedRange>
<citedRange unit="page" from="12" to="13"/>
<citedRange unit="volume">II</citedRange>
<citedRange unit="page">12</citedRange> |
| Example | <bibl>
<ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.
4-5</citedRange>
</bibl> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element citedRange
{
att.global.attributes,
att.pointing.attributes,
att.citing.attributes,
macro.phraseSeq
}⚓ |
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | header: taxonomy |
| Example | <classDecl>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
<!-- ... -->
<textClass>
<keywords scheme="#LCSH">
<term>Political science</term>
<term>United States -- Politics and government —
Revolution, 1775-1783</term>
</keywords>
</textClass> |
| Content model |
<content>
<elementRef key="taxonomy" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element classDecl { att.global.attributes, taxonomy+ }⚓ |
| <collation> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [10.7.1. Object Description] | |||||||
| Module | msdescription — Schema | ||||||
| Attributes |
| ||||||
| Contained by | msdescription: supportDesc | ||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||
| Example | <collation>The written leaves preceded by an original flyleaf,
conjoint with the pastedown.</collation> | ||||||
| Example | <collation>
<p>
<formula>1-5.8 6.6 (catchword, f. 46, does not match following text)
7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>
<catchwords>Catchwords are written horizontally in center
or towards the right lower margin in various manners:
in red ink for quires 1-6 (which are also signed in red
ink with letters of the alphabet and arabic numerals);
quires 7-9 in ink of text within yellow decorated frames;
quire 10 in red decorated frame; quire 12 in ink of text;
quire 13 with red decorative slashes; quire 14 added in
cursive hand.</catchwords>
</p>
</collation> | ||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||
| Schema Declaration |
element collation
{
att.global.attributes,
attribute mainStructures { list { + } }?,
macro.specialPara
}⚓ | ||||||
| <collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: altIdentifier msIdentifier |
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <msIdentifier>
<country>USA</country>
<region>California</region>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<collection>Ellesmere</collection>
<idno>El 26 C 9</idno>
<msName>The Ellesmere Chaucer</msName>
</msIdentifier> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element collection
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
macro.phraseSeq.limited
}⚓ |
| <colophon> (colophon) contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msItem msItemStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <colophon>Ricardus Franciscus Scripsit Anno Domini
1447.</colophon> |
| Example | <colophon>Explicit expliceat/scriptor ludere eat.</colophon> |
| Example | <colophon>Explicit venenum viciorum domini illius, qui comparavit Anno
domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo
sancte Marthe virginis gloriose. Laus tibi criste quia finitur
libellus iste.</colophon> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element colophon
{
att.global.attributes,
att.msExcerpt.attributes,
macro.phraseSeq
}⚓ |
| <condition> (condition) contains a description of the physical condition of the manuscript or object. [10.7.1.5. Condition] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: binding bindingDesc sealDesc supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <condition>
<p>There are lacunae in three places in this
manuscript. After 14v two
leaves has been cut out and narrow strips leaves remains in the spine. After
68v one gathering is missing and after 101v at least one gathering of 8 leaves
has been lost. </p>
<p>Several leaves are damaged with tears or holes or have a
irregular shape. Some of the damages do not allow the lines to be of full
length and they are apparently older than the script. There are tears on fol.
2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,
37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,
74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98
the corner has been torn off. Several leaves are in a bad condition due to
moist and wear, and have become dark, bleached or
wrinkled. </p>
<p>The script has been
touched up in the 17th century with black ink. The touching up on the following
fols. was done by
<name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An
AM-note says according to the lawman
<name>Sigurður Björnsson</name> that the rest of the
touching up was done by himself and another lawman
<name>Sigurður Jónsson</name>.
<name>Sigurður Björnsson</name> did the touching up
on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
<name>Sigurður Jónsson</name> did the rest of the
touching up in the section 36r-59r containing
<title>Bretasögur</title>
</p>
</condition> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element condition { att.global.attributes, macro.specialPara }⚓ |
| <country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | The recommended source for codes to represent coded country names is ISO 3166. | ||||||||||
| Example | <country key="DK">Denmark</country> | ||||||||||
| Schematron |
<sch:rule context="//tei:origin//tei:country[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the country element, when a descendant of origin,
must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element country
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <custEvent> (custodial event) describes a single event during the custodial history of a manuscript or other object. [10.9.1.2. Availability and Custodial History] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: custodialHist | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date>
</custEvent> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element custEvent
{
att.global.attributes,
att.datable.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.specialPara
}⚓ | ||||||||||
| <custodialHist> (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: adminInfo |
| May contain | |
| Example | <custodialHist>
<custEvent type="conservation"
notBefore="1961-03" notAfter="1963-02">Conserved between March 1961 and February 1963 at
Birgitte Dalls Konserveringsværksted.</custEvent>
<custEvent type="photography"
notBefore="1988-05-01" notAfter="1988-05-30">Photographed in
May 1988 by AMI/FA.</custEvent>
<custEvent type="transfer-dispatch"
notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland
13 November 1989.</custEvent>
</custodialHist> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="custEvent" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }⚓ |
| <damage> (damage) contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |
| Module | transcr — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | Since damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon. The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. |
| Example | <l>The Moving Finger wri<damage agent="water" group="1">es; and</damage> having writ,</l>
<l>Moves <damage agent="water" group="1">
<supplied>on: nor all your</supplied>
</damage> Piety nor Wit</l> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element damage
{
att.global.attributes,
att.typed.attributes,
att.damaged.attributes,
macro.paraContent
}⚓ |
| <decoDesc> (decoration description) contains a description of the decoration of a manuscript or other object, either as in paragraphs, or as one or more <decoNote> elements. [10.7.3. Bindings, Seals, and Additional Material] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <decoDesc>
<p>The start of each book of the Bible with a 10-line historiated
illuminated initial; prefaces decorated with 6-line blue initials with red
penwork flourishing; chapters marked by 3-line plain red initials; verses
with 1-line initials, alternately blue or red.</p>
</decoDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="decoNote" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element decoDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, decoNote+ ) )
}⚓ |
| <decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: bibl msdescription: binding bindingDesc decoDesc msItem msItemStruct seal sealDesc | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <decoDesc>
<decoNote type="initial">
<p>The start of each book of the Bible with
a 10-line historiated illuminated initial;
prefaces decorated with 6-line blue initials
with red penwork flourishing; chapters marked by
3-line plain red initials; verses with 1-line initials,
alternately blue or red.</p>
</decoNote>
</decoDesc> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element decoNote
{
att.global.attributes,
att.typed.attribute.subtype,
attribute type
{
"border"
| "diagram"
| "illustration"
| "initial"
| "marginal"
| "micrography"
| "miniature"
| "drawing"
| "rubrication"
| "bas-de-page"
| "map"
| "headpiece"
| "canonTable"
| "carpetPage"
| "histInit"
| "decInit"
| "flourInit"
| "colInit"
| "plainInit"
| "chrysography"
| "lineFill"
| "cadel"
| "instructions"
| "unfilled"
| "none"
| "other"
}?,
macro.specialPara
}⚓ | ||||||||||
| <del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions. The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way. Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21. Certainty, Precision, and Responsibility). There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription. |
| Example | <l>
<del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del>
weht der Wind
</l> |
| Example | <del rend="overstrike">
<gap reason="illegible" quantity="5"
unit="character"/>
</del> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element del
{
att.global.attributes,
att.transcriptional.attributes,
att.typed.attributes,
att.dimensions.attributes,
macro.paraContent
}⚓ |
| <desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components] | |||||||||||||
| Module | core — Schema | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: add corr del desc gap graphic head hi item l lg list listBibl note orig p q quote ref reg sic textLang title unclear linking: seg msdescription: accMat acquisition additions collation condition custEvent decoNote filiation foliation layout musicNotation origin provenance signatures source summary support surrogates typeNote namesdates: listPerson listPlace listRelation place relation | ||||||||||||
| May contain | core: abbr address bibl biblStruct choice cit date desc email expan foreign hi label list listBibl measure name num ptr q quote ref term title figures: table header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||
| Note | When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. | ||||||||||||
| Example | Example of a <desc> element inside a documentation element. <dataSpec module="tei"
ident="teidata.point">
<desc versionDate="2010-10-17"
xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
<!-- ... -->
</dataSpec> | ||||||||||||
| Example | Example of a <desc> element in a non-documentation element. <place xml:id="KERG2">
<placeName>Kerguelen Islands</placeName>
<!-- ... -->
<terrain>
<desc>antarctic tundra</desc>
</terrain>
<!-- ... -->
</place> | ||||||||||||
| Schematron | A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.limitedContent"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element desc
{
att.global.attributes,
att.translatable.attributes,
att.typed.attribute.subtype,
attribute type { "deprecationInfo" }?,
macro.limitedContent
}⚓ | ||||||||||||
| <dimensions> (dimensions) contains a dimensional specification. [10.3.4. Dimensions] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | |||||||||||
| Note | Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification. | ||||||||||
| Example | <dimensions type="leaves">
<height scope="range">157-160</height>
<width>105</width>
</dimensions>
<dimensions type="ruled">
<height scope="most">90</height>
<width scope="most">48</width>
</dimensions>
<dimensions unit="in">
<height>12</height>
<width>10</width>
</dimensions> | ||||||||||
| Example | This element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example: <dimensions type="panels">
<height scope="all">7004</height>
<width scope="all">1803</width>
<dim type="relief" unit="mm">345</dim>
</dimensions> This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm. | ||||||||||
| Example | When simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example: <dimensions type="leaves">
<height scope="range">157-160</height>
<width quantity="105"/>
</dimensions>
<dimensions type="ruled">
<height unit="cm" scope="most"
quantity="90"/>
<width unit="cm" scope="most" quantity="48"/>
</dimensions>
<dimensions unit="in">
<height quantity="12"/>
<width quantity="10"/>
</dimensions> | ||||||||||
| Schematron |
<sch:rule context="//tei:dimensions">
<sch:assert test="@unit" role="error"> The unit of measurement
must be specified in the unit attribute on the dimensions
element </sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:report test="count(tei:width)> 1"> The element <sch:name/> may appear once only
</sch:report>
<sch:report test="count(tei:height)> 1"> The element <sch:name/> may appear once only
</sch:report>
<sch:report test="count(tei:depth)> 1"> The element <sch:name/> may appear once only
</sch:report> | ||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="dim"/>
<classRef key="model.dimLike"/>
</alternate>
</content>
⚓ | ||||||||||
| Schema Declaration |
element dimensions
{
att.global.attributes,
att.dimensions.attributes,
att.typed.attribute.subtype,
attribute type
{
"binding"
| "folia"
| "leaf"
| "line-height"
| "ruled"
| "written"
| "other"
}?,
( dim | model.dimLike )*
}⚓ | ||||||||||
| <distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <distributor>Oxford Text Archive</distributor>
<distributor>Redwood and Burn Ltd</distributor> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element distributor
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq
}⚓ |
| <district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <placeName>
<district type="ward">Jericho</district>
<settlement>Oxford</settlement>
</placeName> | ||||||||||
| Example | <placeName>
<district type="area">South Side</district>
<settlement>Chicago</settlement>
</placeName> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element district
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |
| Module | textstructure — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <body>
<div type="part">
<head>Fallacies of Authority</head>
<p>The subject of which is Authority in various shapes, and the object, to repress all
exercise of the reasoning faculty.</p>
<div n="1" type="chapter">
<head>The Nature of Authority</head>
<p>With reference to any proposed measures having for their object the greatest
happiness of the greatest number [...]</p>
<div n="1.1" type="section">
<head>Analysis of Authority</head>
<p>What on any given occasion is the legitimate weight or influence to be attached to
authority [...] </p>
</div>
<div n="1.2" type="section">
<head>Appeal to Authority, in What Cases Fallacious.</head>
<p>Reference to authority is open to the charge of fallacy when [...] </p>
</div>
</div>
</div>
</body> |
| Schematron |
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report> |
| Schematron |
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
</alternate>
<sequence minOccurs="0">
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate>
<classRef key="model.divLike"/>
<classRef key="model.divGenLike"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1"
maxOccurs="1">
<elementRef key="schemaSpec"/>
<classRef key="model.common"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence minOccurs="0"
maxOccurs="unbounded">
<alternate>
<classRef key="model.divLike"/>
<classRef key="model.divGenLike"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element div
{
att.global.attributes,
att.divLike.attributes,
att.typed.attributes,
att.declaring.attributes,
att.written.attributes,
(
( model.divTop | model.global )*,
(
(
( ( model.divLike | model.divGenLike ), model.global* )+
| (
( ( schemaSpec | model.common ), model.global* )+,
( ( model.divLike | model.divGenLike ), model.global* )*
)
),
( model.divBottom, model.global* )*
)?
)
}⚓ |
| <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: editionStmt |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element edition { att.global.attributes, macro.phraseSeq }⚓ |
| <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <editionStmt>
<edition n="S2">Students' edition</edition>
<respStmt>
<resp>Adapted by </resp>
<name>Elizabeth Kirk</name>
</respStmt>
</editionStmt> |
| Example | <editionStmt>
<p>First edition, <date>Michaelmas Term, 1991.</date>
</p>
</editionStmt> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="edition"/>
<classRef key="model.respLike"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element editionStmt
{
att.global.attributes,
( model.pLike+ | ( edition, model.respLike* ) )
}⚓ |
| <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors] | |||||||||||
| Module | core — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. | ||||||||||
| Example | <editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element editor
{
att.global.attributes,
att.naming.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p header: interpretation |
| Example | <editorialDecl>
<normalization>
<p>All words converted to Modern American spelling using
Websters 9th Collegiate dictionary
</p>
</normalization>
<quotation marks="all">
<p>All opening quotation marks converted to “ all closing
quotation marks converted to &cdq;.</p>
</quotation>
</editorialDecl> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<classRef key="model.editorialDeclPart"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element editorialDecl
{
att.global.attributes,
att.declarable.attributes,
( model.pLike | model.editorialDeclPart )+
}⚓ |
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | |
| Example | <encodingDesc>
<p>Basic encoding, capturing lexical information only. All
hyphenation, punctuation, and variant spellings normalized. No
formatting or layout information preserved.</p>
</encodingDesc> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.encodingDescPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element encodingDesc
{
att.global.attributes,
( model.encodingDescPart | model.pLike )+
}⚓ |
| <explicit> (explicit) contains the explicit of a item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: bibl msdescription: msItem msItemStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <explicit>sed libera nos a malo.</explicit>
<rubric>Hic explicit oratio qui dicitur dominica.</rubric>
<explicit type="defective">ex materia quasi et forma sibi
proporti<gap/>
</explicit>
<explicit type="reverse">saued be shulle that doome of day the at
</explicit> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element explicit
{
att.global.attributes,
att.typed.attributes,
att.msExcerpt.attributes,
macro.phraseSeq
}⚓ |
| <extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent>
<extent>ten 3.5 inch high density diskettes</extent> |
| Example | The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned. <extent>
<measure unit="MiB" quantity="4.2">About four megabytes</measure>
<measure unit="pages" quantity="245">245 pages of source
material</measure>
</extent> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element extent { att.global.attributes, macro.phraseSeq }⚓ |
| <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles] | |
| Module | transcr — Schema |
| Attributes |
|
| Member of | |
| Contained by | textstructure: TEI |
| May contain | |
| Example | <facsimile>
<graphic url="page1.png"/>
<surface>
<graphic url="page2-highRes.png"/>
<graphic url="page2-lowRes.png"/>
</surface>
<graphic url="page3.png"/>
<graphic url="page4.png"/>
</facsimile> |
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="200" lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
</facsimile> |
| Schematron |
<sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
<sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
transcribed text should not be present within it.
</sch:report>
</sch:rule> |
| Content model |
<content>
<sequence>
<elementRef key="front" minOccurs="0"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.graphicLike"/>
<elementRef key="surface"/>
<elementRef key="surfaceGrp"/>
</alternate>
<elementRef key="back" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element facsimile
{
att.global.attributes,
att.declaring.attributes,
( front?, ( model.graphicLike | surface | surfaceGrp )+, back? )
}⚓ |
| <fallback> Wrapper for fallback elements if an XInclude fails | |
| Namespace | http://www.w3.org/2001/XInclude |
| Module | derived-module-msdesc |
| Contained by | derived-module-msdesc: include |
| May contain | ANY |
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<textNode/>
<anyElement/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element fallback { text | anyElement_fallback_1 }⚓ |
| <figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images] | |
| Module | figures — Schema |
| Attributes |
|
| Contained by | figures: figure |
| May contain | core: abbr address bibl biblStruct choice cit date desc email expan foreign hi label list listBibl measure name num ptr q quote ref term title figures: table header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes. |
| Example | <figure>
<graphic url="emblem1.png"/>
<head>Emblemi d'Amore</head>
<figDesc>A pair of naked winged cupids, each holding a
flaming torch, in a rural setting.</figDesc>
</figure> |
| Content model |
<content>
<macroRef key="macro.limitedContent"/>
</content>
⚓ |
| Schema Declaration |
element figDesc { att.global.attributes, macro.limitedContent }⚓ |
| <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images] | |
| Module | figures — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear gaiji: glyph header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Example | <figure>
<head>The View from the Bridge</head>
<figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
<graphic url="http://www.example.org/fig1.png"
scale="0.5"/>
</figure> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.headLike"/>
<classRef key="model.common"/>
<elementRef key="figDesc"/>
<classRef key="model.graphicLike"/>
<classRef key="model.global"/>
<classRef key="model.divBottom"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element figure
{
att.global.attributes,
att.placement.attributes,
att.typed.attributes,
att.written.attributes,
(
model.headLike
| model.common
| figDesc
| model.graphicLike
| model.global
| model.divBottom
)*
}⚓ |
| <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | |
| Note | The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
| Example | <fileDesc>
<titleStmt>
<title>The shortest possible TEI document</title>
</titleStmt>
<publicationStmt>
<p>Distributed as part of TEI P5</p>
</publicationStmt>
<sourceDesc>
<p>No print source exists: this is an original digital text</p>
</sourceDesc>
</fileDesc> |
| Content model |
<content>
<sequence>
<sequence>
<elementRef key="titleStmt"/>
<elementRef key="editionStmt"
minOccurs="0"/>
<elementRef key="extent" minOccurs="0"/>
<elementRef key="publicationStmt"/>
<elementRef key="seriesStmt"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="notesStmt"
minOccurs="0"/>
</sequence>
<elementRef key="sourceDesc"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element fileDesc
{
att.global.attributes,
(
(
titleStmt,
editionStmt?,
extent?,
publicationStmt,
seriesStmt*,
notesStmt?
),
sourceDesc+
)
}⚓ |
| <filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msItem msItemStruct |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <msContents>
<msItem>
<title>Beljakovski sbornik</title>
<filiation type="protograph">Bulgarian</filiation>
<filiation type="antigraph">Middle Bulgarian</filiation>
<filiation type="apograph">
<ref target="#DN17">Dujchev N 17</ref>
</filiation>
</msItem>
</msContents>
<!-- ... -->
<msDesc xml:id="DN17">
<msIdentifier>
<settlement>Faraway</settlement>
</msIdentifier>
<!-- ... -->
</msDesc> In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17. |
| Example | <msItem>
<title>Guan-ben</title>
<filiation>
<p>The "Guan-ben" was widely current among mathematicians in the
Qing dynasty, and "Zhao Qimei version" was also read. It is
therefore difficult to know the correct filiation path to follow.
The study of this era is much indebted to Li Di. We explain the
outline of his conclusion here. Kong Guangsen
(1752-1786)(17) was from the same town as Dai Zhen, so he obtained
"Guan-ben" from him and studied it(18). Li Huang (d. 1811)
(19) took part in editing Si Ku Quan Shu, so he must have had
"Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,
and studied "Da Yan Zong Shu Shu" (The General Dayan
Computation). He wrote Jiu Yi Suan Shu (Mathematics
Searching for One, 1803) based on this version of Shu Xue Jiu
Zhang (20).</p>
<p>One of the most important persons in restoring our knowledge
concerning the filiation of these books was Li Rui (1768(21)
-1817)(see his biography). ... only two volumes remain of this
manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,
question 2 of "Huan Tian San Ji" (square of three loops),
which later has been lost.</p>
</filiation>
</msItem>
<!--http://www2.nkfust.edu.tw/~jochi/ed1.htm--> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element filiation
{
att.global.attributes,
att.typed.attributes,
macro.specialPara
}⚓ |
| <finalRubric> (final rubric) contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msItem msItemStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <finalRubric>Explicit le romans de la Rose ou l'art
d'amours est toute enclose.</finalRubric>
<finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element finalRubric
{
att.global.attributes,
att.typed.attributes,
att.msExcerpt.attributes,
macro.phraseSeq
}⚓ |
| <foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [10.7.1.4. Foliation] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <foliation>Contemporary foliation in red
roman numerals in the centre
of the outer margin.</foliation> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element foliation
{
att.datable.attributes,
att.global.attributes,
macro.specialPara
}⚓ |
| <foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification. This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
| Example | This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>? |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element foreign { att.global.attributes, macro.phraseSeq }⚓ |
| <formula> (formula) contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions] | |
| Module | figures — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author biblScope cit citedRange corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear gaiji: glyph header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Example | <formula notation="tex">$E=mc^2$</formula> |
| Example | <formula notation="none">E=mc<hi rend="sup">2</hi>
</formula> |
| Example | <formula notation="mathml">
<m:math>
<m:mi>E</m:mi>
<m:mo>=</m:mo>
<m:mi>m</m:mi>
<m:msup>
<m:mrow>
<m:mi>c</m:mi>
</m:mrow>
<m:mrow>
<m:mn>2</m:mn>
</m:mrow>
</m:msup>
</m:math>
</formula> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.graphicLike"/>
<classRef key="model.hiLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element formula
{
att.global.attributes,
att.notated.attributes,
( text | model.graphicLike | model.hiLike )*
}⚓ |
| <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement] | |||||||||||
| Module | header — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority. | ||||||||||
| Example | <funder>The National Endowment for the Humanities, an independent federal agency</funder>
<funder>Directorate General XIII of the Commission of the European Communities</funder>
<funder>The Andrew W. Mellon Foundation</funder>
<funder>The Social Sciences and Humanities Research Council of Canada</funder> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element funder
{
att.global.attributes,
att.canonical.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq.limited
}⚓ | ||||||||||
| <fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter] | |||||||||||
| Module | transcr — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance. | ||||||||||
| Example | <fw type="sig" place="bottom">C3</fw> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element fw
{
att.global.attributes,
att.typed.attribute.subtype,
att.placement.attributes,
att.written.attributes,
attribute type { text }?,
macro.phraseSeq
}⚓ | ||||||||||
| <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes] | |||||||
| Module | gaiji — Schema | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg series sic street term textLang title unclear figures: cell gaiji: mapping header: change distributor edition extent handNote idno licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote depth dim explicit filiation finalRubric foliation height heraldry incipit layout locus material msName musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark width | ||||||
| May contain | Character data only | ||||||
| Note | The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph. | ||||||
| Example | <g ref="#ctlig">ct</g> This example points to a <glyph> element with the identifier ctlig like the following: <glyph xml:id="ctlig">
<!-- here we describe the particular ct-ligature intended -->
</glyph> | ||||||
| Example | <g ref="#per-glyph">per</g> The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows: <glyph xml:id="per-glyph">
<!-- ... -->
</glyph> | ||||||
| Content model |
<content>
<textNode/>
</content>
⚓ | ||||||
| Schema Declaration |
element g
{
att.global.attributes,
att.typed.attributes,
attribute ref { text }?,
text
}⚓ | ||||||
| <gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||
| Module | core — Schema | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||
| May contain | core: desc | ||||||||||||||||
| Note | The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion. | ||||||||||||||||
| Example | <gap quantity="4" unit="chars"
reason="illegible"/> | ||||||||||||||||
| Example | <gap quantity="1" unit="essay"
reason="sampling"/> | ||||||||||||||||
| Example | <del>
<gap atLeast="4" atMost="8" unit="chars"
reason="illegible"/>
</del> | ||||||||||||||||
| Example | <gap extent="several lines" reason="lost"/> | ||||||||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.descLike"/>
<classRef key="model.certLike"/>
</alternate>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element gap
{
att.global.attributes,
att.timed.attributes,
att.editLike.attributes,
att.dimensions.attributes,
attribute reason
{
list
{
(
"cancelled"
| "deleted"
| "editorial"
| "illegible"
| "inaudible"
| "irrelevant"
| "sampling"
)+
}
}?,
attribute agent { text }?,
( model.descLike | model.certLike )*
}⚓ | ||||||||||||||||
| <geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location] | |
| Module | namesdates — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | Character data only |
| Note | Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System. |
| Example | <geoDecl xml:id="WGS" datum="WGS84">World Geodetic System</geoDecl>
<geoDecl xml:id="OS" datum="OSGB36">Ordnance Survey</geoDecl>
<!-- ... -->
<location>
<desc>A tombstone plus six lines of
Anglo-Saxon text, built into the west tower (on the south side
of the archway, at 8 ft. above the ground) of the
Church of St. Mary-le-Wigford in Lincoln.</desc>
<geo decls="#WGS">53.226658 -0.541254</geo>
<geo decls="#OS">SK 97481 70947</geo>
</location> |
| Example | <geo>41.687142 -74.870109</geo> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element geo { att.global.attributes, att.declaring.attributes, text }⚓ |
| <geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element geogFeat
{
att.datable.attributes,
att.editLike.attributes,
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.dimensions.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <geogName>
<geogFeat>Mount</geogFeat>
<name>Sinai</name>
</geogName> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element geogName
{
att.datable.attributes,
att.editLike.attributes,
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <gi> (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.5. Element Specifications] | |||||||||
| Module | tagdocs — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||
| May contain | XSD Name | ||||||||
| Example | <p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the
<gi scheme="DBK">listItem</gi> element.</p> This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted. | ||||||||
| Content model |
<content>
<dataRef key="teidata.name"/>
</content>
⚓ | ||||||||
| Schema Declaration |
element gi { att.global.attributes, attribute scheme { text }?, teidata.name }⚓ | ||||||||
| <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji — Schema |
| Attributes |
|
| Contained by | gaiji: charDecl |
| May contain | |
| Example | <glyph xml:id="rstroke">
<localProp name="Name"
value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>
<localProp name="entity" value="rstroke"/>
<figure>
<graphic url="glyph-rstroke.png"/>
</figure>
</glyph> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="unicodeProp"/>
<elementRef key="unihanProp"/>
<elementRef key="localProp"/>
<elementRef key="mapping"/>
<elementRef key="figure"/>
<classRef key="model.graphicLike"/>
<classRef key="model.noteLike"/>
<classRef key="model.descLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element glyph
{
att.global.attributes,
(
unicodeProp
| unihanProp
| localProp
| mapping
| figure
| model.graphicLike
| model.noteLike
| model.descLike
)*
}⚓ |
| <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author biblScope cit citedRange corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear gaiji: glyph header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material msItem musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: desc |
| Note | The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded. |
| Example | <figure>
<graphic url="fig1.png"/>
<head>Figure One: The View from the Bridge</head>
<figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
</figure> |
| Example | <facsimile>
<surfaceGrp n="leaf1">
<surface>
<graphic url="page1.png"/>
</surface>
<surface>
<graphic url="page2-highRes.png"/>
<graphic url="page2-lowRes.png"/>
</surface>
</surfaceGrp>
</facsimile> |
| Example | <facsimile>
<surfaceGrp n="leaf1" xml:id="spi001">
<surface xml:id="spi001r">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001r.jpg"/>
<graphic type="normal" subtype="low-res"
url="spi/normal/lowRes/001r.jpg"/>
<graphic type="normal"
subtype="high-res" url="spi/normal/highRes/001r.jpg"/>
<graphic type="high-contrast"
subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/>
<graphic type="high-contrast"
subtype="high-res" url="spi/contrast/highRes/001r.jpg"/>
</surface>
<surface xml:id="spi001v">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001v.jpg"/>
<graphic type="normal" subtype="low-res"
url="spi/normal/lowRes/001v.jpg"/>
<graphic type="normal"
subtype="high-res" url="spi/normal/highRes/001v.jpg"/>
<graphic type="high-contrast"
subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/>
<graphic type="high-contrast"
subtype="high-res" url="spi/contrast/highRes/001v.jpg"/>
<zone xml:id="spi001v_detail01">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/>
<graphic type="normal"
subtype="low-res"
url="spi/normal/lowRes/001v-detail01.jpg"/>
<graphic type="normal"
subtype="high-res"
url="spi/normal/highRes/001v-detail01.jpg"/>
<graphic type="high-contrast"
subtype="low-res"
url="spi/contrast/lowRes/001v-detail01.jpg"/>
<graphic type="high-contrast"
subtype="high-res"
url="spi/contrast/highRes/001v-detail01.jpg"/>
</zone>
</surface>
</surfaceGrp>
</facsimile> |
| Content model |
<content>
<classRef key="model.descLike"
minOccurs="0" maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element graphic
{
att.global.attributes,
att.media.attributes,
att.resourced.attributes,
att.declaring.attributes,
att.typed.attributes,
model.descLike*
}⚓ |
| <handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations] | |||||||
| Module | msdescription — Schema | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | msdescription: physDesc | ||||||
| May contain | |||||||
| Example | <handDesc>
<handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote>
</handDesc> | ||||||
| Example | <handDesc hands="2">
<p>The manuscript is written in two contemporary hands, otherwise
unknown, but clearly those of practised scribes. Hand I writes
ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably
Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand
on f. 24, but the evidence for this is insubstantial.</p>
</handDesc> | ||||||
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="handNote" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ | ||||||
| Schema Declaration |
element handDesc
{
att.global.attributes,
attribute hands { text }?,
( model.pLike+ | ( summary?, handNote+ ) )
}⚓ | ||||||
| <handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations] | |||||||||||||||||||
| Module | header — Schema | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Contained by | msdescription: handDesc | ||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||
| Example | <handNote scope="sole">
<p>Written in insular
phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
minuscule.</p>
</handNote> | ||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||||||||||
| Schema Declaration |
element handNote
{
att.global.attributes,
att.handFeatures.attribute.scribe,
att.handFeatures.attribute.scribeRef,
att.handFeatures.attribute.scriptRef,
att.handFeatures.attribute.medium,
att.handFeatures.attribute.scope,
attribute script
{
list
{
(
"capitalsSquare"
| "capitalsRustic"
| "uncial"
| "halfUncial"
| "minusculeInsular"
| "minusculeVernacular"
| "minusculeCaroline"
| "minuscule"
| "protogothic"
| "textualisNorthern"
| "textualisSouthern"
| "semitextualis"
| "cursivaAntiquior"
| "cursiva"
| "hybrida"
| "gothicoAntiqua"
| "humanistica"
| "humanisticaTextualis"
| "humanisticaSemitextualis"
| "humanisticaCursiva"
)+
}
}?,
attribute execution { "formata" | "libraria" | "currens" }?,
macro.specialPara
}⚓ | ||||||||||||||||||
| <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section. |
| Example | The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example: <div1 n="I" type="book">
<head>In the name of Christ here begins the first book of the ecclesiastical history of
Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
<div2 type="section">
<head>In the name of Christ here begins Book I of the history.</head>
<p>Proposing as I do ...</p>
<p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
years passed.</p>
<trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
years from the beginning of the world down to the death of Saint Martin.</trailer>
</div2>
</div1> |
| Example | When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute. <div type="subsection">
<head place="margin">Secunda conclusio</head>
<p>
<lb n="1251"/>
<hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
</hi>
<lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
[...]
</p>
</div> |
| Example | The <head> element is also used to mark headings of other units, such as lists: With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
<head>Connectives</head>
<item>above</item>
<item>accordingly</item>
<item>across from</item>
<item>adjacent to</item>
<item>again</item>
<item>
<!-- ... -->
</item>
</list> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<elementRef key="lg"/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.lLike"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element head
{
att.global.attributes,
att.typed.attributes,
att.placement.attributes,
att.written.attributes,
(
text
| lg
| model.gLike
| model.phrase
| model.inter
| model.lLike
| model.global
)*
}⚓ |
| <history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | |
| May contain | core: p msdescription: acquisition origin provenance summary |
| Example | <history>
<origin>
<p>Written in Durham during the mid twelfth
century.</p>
</origin>
<provenance>
<p>Recorded in two medieval
catalogues of the books belonging to Durham Priory, made in 1391 and
1405.</p>
</provenance>
<provenance>
<p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
according to inscriptions on ff. 4v and 5.</p>
</provenance>
<acquisition>
<p>Presented to Trinity College in 1738 by
Thomas Gale and his son Roger.</p>
</acquisition>
</history> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="origin" minOccurs="0"/>
<elementRef key="provenance"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="acquisition"
minOccurs="0"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element history
{
att.global.attributes,
( model.pLike+ | ( summary?, origin?, provenance*, acquisition? ) )
}⚓ |
| <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||||||||||||
| Module | header — Schema | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine address analytic author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure monogr name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote idno language licence principal publicationStmt scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||||
| May contain | |||||||||||||||||||||
| Note | <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI. | ||||||||||||||||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
<g ref="#sym"/>345
</idno> In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym. | ||||||||||||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="idno"/>
</alternate>
</content>
⚓ | ||||||||||||||||||||
| Schema Declaration |
element idno
{
att.global.attributes,
att.sortable.attributes,
att.datable.attributes,
att.typed.attribute.subtype,
attribute type
{
"ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
}?,
attribute calendar { list { + } }?,
( text | model.gLike | idno )*
}⚓ | ||||||||||||||||||||
| <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Schema |
| Attributes |
|
| Contained by | core: monogr |
| May contain | |
| Example | <imprint>
<pubPlace>Oxford</pubPlace>
<publisher>Clarendon Press</publisher>
<date>1987</date>
</imprint> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="classCode"/>
<elementRef key="catRef"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate>
<classRef key="model.imprintPart"/>
<classRef key="model.dateLike"/>
</alternate>
<elementRef key="respStmt" minOccurs="0"
maxOccurs="unbounded"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element imprint
{
att.global.attributes,
(
( classCode | catRef )*,
( ( model.imprintPart | model.dateLike ), respStmt*, model.global* )+
)
}⚓ |
| <incipit> contains the incipit of a manuscript or similar object item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: bibl msdescription: msItem msItemStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <incipit>Pater noster qui es in celis</incipit>
<incipit defective="true">tatem dedit hominibus alleluia.</incipit>
<incipit type="biblical">Ghif ons huden onse dagelix broet</incipit>
<incipit>O ongehoerde gewerdighe christi</incipit>
<incipit type="lemma">Firmiter</incipit>
<incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element incipit
{
att.global.attributes,
att.typed.attributes,
att.msExcerpt.attributes,
macro.phraseSeq
}⚓ |
| <include> The W3C XInclude element | |||||||||||||||||||||||||||||||||||||||||||
| Namespace | http://www.w3.org/2001/XInclude | ||||||||||||||||||||||||||||||||||||||||||
| Module | derived-module-msdesc | ||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||||||||||||
| Contained by | |||||||||||||||||||||||||||||||||||||||||||
| May contain | derived-module-msdesc: fallback | ||||||||||||||||||||||||||||||||||||||||||
| Content model |
<content>
<elementRef key="fallback" minOccurs="0"
maxOccurs="1"/>
</content>
⚓ | ||||||||||||||||||||||||||||||||||||||||||
| Schema Declaration |
element include
{
attribute href { text }?,
attribute parse { "xml" | "text" }?,
attribute xpointer { text }?,
attribute encoding { text }?,
attribute accept { text }?,
attribute accept-charset { text }?,
attribute accept-language { text }?,
fallback?
}⚓ | ||||||||||||||||||||||||||||||||||||||||||
| <institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: altIdentifier msIdentifier |
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <msIdentifier>
<settlement>Oxford</settlement>
<institution>University of Oxford</institution>
<repository>Bodleian Library</repository>
<idno>MS. Bodley 406</idno>
</msIdentifier> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element institution
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq.limited
}⚓ |
| <interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: editorialDecl |
| May contain | core: p |
| Example | <interpretation>
<p>The part of speech analysis applied throughout section 4 was added by hand and has not
been checked</p>
</interpretation> |
| Content model |
<content>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element interpretation
{
att.global.attributes,
att.declarable.attributes,
model.pLike+
}⚓ |
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
| Module | core — Schema |
| Attributes |
|
| Contained by | core: list |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n. |
| Example | <list rend="numbered">
<head>Here begin the chapter headings of Book IV</head>
<item n="4.1">The death of Queen Clotild.</item>
<item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
<item n="4.3">The wives and children of Lothar.</item>
<item n="4.4">The Counts of the Bretons.</item>
<item n="4.5">Saint Gall the Bishop.</item>
<item n="4.6">The priest Cato.</item>
<item> ...</item>
</list> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element item
{
att.global.attributes,
att.sortable.attributes,
macro.specialPara
}⚓ |
| <keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification] | |||||||
| Module | header — Schema | ||||||
| Attributes |
| ||||||
| Contained by | header: textClass | ||||||
| May contain | |||||||
| Note | Each individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within an <item> inside a <list> is permitted for backwards compatibility, but is deprecated. If no control list exists for the keywords used, then no value should be supplied for the scheme attribute. | ||||||
| Example | <keywords scheme="http://classificationweb.net">
<term>Babbage, Charles</term>
<term>Mathematicians - Great Britain - Biography</term>
</keywords> | ||||||
| Example | <keywords>
<term>Fermented beverages</term>
<term>Central Andes</term>
<term>Schinus molle</term>
<term>Molle beer</term>
<term>Indigenous peoples</term>
<term>Ethnography</term>
<term>Archaeology</term>
</keywords> | ||||||
| Content model |
<content>
<alternate>
<elementRef key="term" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="list"/>
</alternate>
</content>
⚓ | ||||||
| Schema Declaration |
element keywords
{
att.global.attributes,
attribute scheme { text }?,
( term+ | list )
}⚓ | ||||||
| <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: change handNote licence scriptNote linking: seg |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi label lb list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l> |
| Schematron |
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
</sch:report> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element l
{
att.global.attributes,
att.fragmentable.attributes,
( text | model.gLike | model.phrase | model.inter | model.global )*
}⚓ |
| <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: add corr del desc head hi item l lg list note orig p q quote ref reg sic textLang title unclear header: change handNote licence scriptNote linking: seg msdescription: accMat acquisition additions collation condition custEvent decoNote filiation foliation layout musicNotation origin provenance signatures source summary support surrogates typeNote namesdates: place |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin: <list type="gloss" xml:lang="enm">
<head xml:lang="en">Vocabulary</head>
<headLabel xml:lang="en">Middle English</headLabel>
<headItem xml:lang="en">New English</headItem>
<label>nu</label>
<item xml:lang="en">now</item>
<label>lhude</label>
<item xml:lang="en">loudly</item>
<label>bloweth</label>
<item xml:lang="en">blooms</item>
<label>med</label>
<item xml:lang="en">meadow</item>
<label>wude</label>
<item xml:lang="en">wood</item>
<label>awe</label>
<item xml:lang="en">ewe</item>
<label>lhouth</label>
<item xml:lang="en">lows</item>
<label>sterteth</label>
<item xml:lang="en">bounds, frisks (cf. <cit>
<ref>Chaucer, K.T.644</ref>
<quote>a courser, <term>sterting</term>as the fyr</quote>
</cit>
</item>
<label>verteth</label>
<item xml:lang="la">pedit</item>
<label>murie</label>
<item xml:lang="en">merrily</item>
<label>swik</label>
<item xml:lang="en">cease</item>
<label>naver</label>
<item xml:lang="en">never</item>
</list> |
| Example | Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element: I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
<label>(1)</label>
<item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
<label>(2) </label>
<item>Not a sheet has been seen by any human eyes, excepting those of the author and the
printer: the faults and the merits are exclusively my own.</item>
</list> |
| Example | Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon: <list type="gloss">
<label>March 1757.</label>
<item>I wrote some critical observations upon Plautus.</item>
<label>March 8th.</label>
<item>I wrote a long dissertation upon some lines of Virgil.</item>
<label>June.</label>
<item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
amori.</quote>
</item>
<label>August.</label>
<item>I went to Crassy, and staid two days.</item>
</list> Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice. |
| Example | Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it. <p>[...]
<lb/>& n’entrer en mauuais & mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
entre les Romains.</label>
<lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p> In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label. |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element label
{
att.global.attributes,
att.typed.attributes,
att.placement.attributes,
att.written.attributes,
macro.phraseSeq
}⚓ |
| <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Example | <langUsage>
<language ident="fr-CA" usage="60">Québecois</language>
<language ident="en-CA" usage="20">Canadian business English</language>
<language ident="en-GB" usage="20">British English</language>
</langUsage> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="language" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element langUsage
{
att.global.attributes,
att.declarable.attributes,
( model.pLike+ | language+ )
}⚓ |
| <language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage] | |||||||||||||
| Module | header — Schema | ||||||||||||
| Attributes |
| ||||||||||||
| Contained by | header: langUsage | ||||||||||||
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||
| Note | Particularly for sublanguages, an informal prose characterization should be supplied as content for the element. | ||||||||||||
| Example | <langUsage>
<language ident="en-US" usage="75">modern American English</language>
<language ident="az-Arab" usage="20">Azerbaijani in Arabic script</language>
<language ident="x-lap" usage="05">Pig Latin</language>
</langUsage> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element language
{
att.global.attributes,
attribute ident { text },
attribute usage { text }?,
macro.phraseSeq.limited
}⚓ | ||||||||||||
| <layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations] | |||||||||||||||||||||||||||||||||||||||||||||||
| Module | msdescription — Schema | ||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||
| Contained by | msdescription: layoutDesc | ||||||||||||||||||||||||||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||||||||||||||||||||||||||||||
| Example | <layout columns="1" ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout> | ||||||||||||||||||||||||||||||||||||||||||||||
| Example | <layout columns="2" ruledLines="42">
<p>2 columns of 42 lines ruled in ink, with central rule
between the columns.</p>
</layout> | ||||||||||||||||||||||||||||||||||||||||||||||
| Example | <layout columns="1 2" writtenLines="40 50">
<p>Some pages have 2 columns, with central rule
between the columns; each column with between 40 and 50 lines of writing.</p>
</layout> | ||||||||||||||||||||||||||||||||||||||||||||||
| Example | <layout streams="3" columns="3"/>
<!-- Further down in document body -->
<div type="page">
<ab>
<pb/>
一二三<cb type="top-stream"/>
一二三<cb type="mid-stream"/>
一二三<cb type="bottom-stream"/>
<!-- cb here for demo purposes -->
</ab>
</div> | ||||||||||||||||||||||||||||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||||||||||||||||||||||||||||||||||||||
| Schema Declaration |
element layout
{
att.typed.attributes,
att.global.attributes,
attribute topLine { "above" | "below" | "mixed" }?,
attribute rulingMedium
{
"ink" | "leadpoint" | "hardpoint" | "crayon" | "mixed" | "board"
}?,
attribute columns { list { ? } }?,
attribute streams { list { ? } }?,
attribute ruledLines { list { ? } }?,
attribute writtenLines { list { ? } }?,
macro.specialPara
}⚓ | ||||||||||||||||||||||||||||||||||||||||||||||
| <layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: objectDesc |
| May contain | |
| Example | <layoutDesc>
<p>Most pages have between 25 and 32 long lines ruled in lead.</p>
</layoutDesc> |
| Example | <layoutDesc>
<layout columns="2" ruledLines="42">
<p>
<locus from="f12r" to="f15v"/>
2 columns of 42 lines pricked and ruled in ink, with
central rule between the columns.</p>
</layout>
<layout columns="3">
<p>
<locus from="f16"/>Prickings for three columns are visible.</p>
</layout>
</layoutDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="layout" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element layoutDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, layout+ ) )
}⚓ |
| <lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | Empty element |
| Note | By convention, <lb> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked. The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives. |
| Example | This example shows typographical line breaks within metrical lines, where they occur at different places in different editions: <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> |
| Example | This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word. <titlePart>
<lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element lb
{
att.global.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
}⚓ |
| <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: change handNote licence scriptNote linking: seg |
| May contain | |
| Note | contains verse lines or nested line groups only, possibly prefixed by a heading. |
| Example | <lg type="free">
<l>Let me be my own fool</l>
<l>of my own making, the sum of it</l>
</lg>
<lg type="free">
<l>is equivocal.</l>
<l>One says of the drunken farmer:</l>
</lg>
<lg type="free">
<l>leave him lay off it. And this is</l>
<l>the explanation.</l>
</lg> |
| Schematron |
<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) >
0">An lg element
must contain at least one child l, lg, or gap element.</sch:assert> |
| Schematron |
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups.
</sch:report> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
</alternate>
<alternate>
<classRef key="model.lLike"/>
<classRef key="model.stageLike"/>
<classRef key="model.labelLike"/>
<classRef key="model.pPart.transcriptional"/>
<elementRef key="lg"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.lLike"/>
<classRef key="model.stageLike"/>
<classRef key="model.labelLike"/>
<classRef key="model.pPart.transcriptional"/>
<classRef key="model.global"/>
<elementRef key="lg"/>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element lg
{
att.global.attributes,
att.divLike.attributes,
att.typed.attributes,
att.declaring.attributes,
(
( model.divTop | model.global )*,
(
model.lLike
| model.stageLike
| model.labelLike
| model.pPart.transcriptional
| lg
),
(
model.lLike
| model.stageLike
| model.labelLike
| model.pPart.transcriptional
| model.global
| lg
)*,
( model.divBottom, model.global* )*
)
}⚓ |
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |||||||||||
| Module | header — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | header: availability | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. | ||||||||||
| Example | <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence> | ||||||||||
| Example | <availability>
<licence target="http://creativecommons.org/licenses/by/3.0/"
notBefore="2013-01-01">
<p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
applies to this document.</p>
<p>The licence was added on January 1, 2013.</p>
</licence>
</availability> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element licence
{
att.global.attributes,
att.pointing.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.specialPara
}⚓ | ||||||||||
| <list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||||
| Module | core — Schema | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | linking: seg | ||||||||||||
| May contain | |||||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||||
| Example | <list rend="numbered">
<item>a butcher</item>
<item>a baker</item>
<item>a candlestick maker, with
<list rend="bulleted">
<item>rings on his fingers</item>
<item>bells on his toes</item>
</list>
</item>
</list> | ||||||||||||
| Example | <list type="syllogism" rend="bulleted">
<item>All Cretans are liars.</item>
<item>Epimenides is a Cretan.</item>
<item>ERGO Epimenides is a liar.</item>
</list> | ||||||||||||
| Example | <list type="litany" rend="simple">
<item>God save us from drought.</item>
<item>God save us from pestilence.</item>
<item>God save us from wickedness in high places.</item>
<item>Praise be to God.</item>
</list> | ||||||||||||
| Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section">
<head>Athelstan's Ordinance</head>
<list rend="numbered">
<item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
eightpence.
<list rend="numbered">
<item n="1.1">And if anyone does spare one, he is to pay for the thief with his
wergild — and the thief is to be no nearer a settlement on that account — or to
clear himself by an oath of that amount.</item>
<item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
not to be spared [whether younger or older than twelve].</item>
<item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
then be redeemed with 120 shillings; and the kindred are to stand surety for him
that he will desist for ever.</item>
<item n="1.4">And if he steals after that, they are to pay for him with his wergild,
or to bring him back there.</item>
<item n="1.5">And if he steals after that, they are to pay for him with his wergild,
whether to the king or to him to whom it rightly belongs; and everyone of those who
supported him is to pay 120 shillings to the king as a fine.</item>
</list>
</item>
<item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
no justice can be obtained, that one should order their kindred to fetch back such a
person to justice and to find him a lord in public meeting.
<list rend="numbered">
<item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
he is then to be a fugitive afterwards, and he who encounters him is to strike him
down as a thief.</item>
<item n="2.2">And he who harbours him after that, is to pay for him with his wergild
or to clear himself by an oath of that amount.</item>
</list>
</item>
<item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
his guilty man, so that the king is appealed to, is to repay the value of the goods and
120 shillings to the king; and he who appeals to the king before he demands justice as
often as he ought, is to pay the same fine as the other would have done, if he had
refused him justice.
<list rend="numbered">
<item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
known about him, is to forfeit the slave and be liable to his wergild on the first
occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
<item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
an accessory of thieves who have committed theft, is to liable to the same.</item>
</list>
</item>
<item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
afterwards convicted at the three-fold ordeal.</item>
</list>
</div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. | ||||||||||||
| Example | <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross.
<list rend="simple">
<item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
subscribed to the pious and catholic validity of this document with the sign of the Holy
Cross.</item>
<item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
the sign of the Holy Cross.</item>
<item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
sign of the Holy Cross.</item>
<item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
sign of the Holy Cross.</item>
<item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
the Holy Cross.</item>
<item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
<item>I, Æthelwine, bishop, have subscribed through delegates.</item>
<item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
Cross.</item>
</list>
</p> | ||||||||||||
| Schematron |
<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule> | ||||||||||||
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
</alternate>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="item"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence>
<elementRef key="headLabel"
minOccurs="0"/>
<elementRef key="headItem"
minOccurs="0"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="label"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="item"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element list
{
att.global.attributes,
att.sortable.attributes,
att.typed.attribute.subtype,
attribute type
{
"gloss" | "index" | "instructions" | "litany" | "syllogism"
}?,
(
( model.divTop | model.global | desc* )*,
(
( item, model.global* )+
| (
headLabel?,
headItem?,
( label, model.global*, item, model.global* )+
)
),
( model.divBottom, model.global* )*
)
}⚓ | ||||||||||||
| <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: add cit corr del desc head hi item l listBibl note orig p q quote ref reg relatedItem sic textLang title unclear header: change handNote licence scriptNote sourceDesc taxonomy linking: seg |
| May contain | |
| Example | <listBibl>
<head>Works consulted</head>
<bibl>Blain, Clements and Grundy: Feminist Companion to
Literature in English (Yale, 1990)
</bibl>
<biblStruct>
<analytic>
<title>The Interesting story of the Children in the Wood</title>
</analytic>
<monogr>
<title>The Penny Histories</title>
<author>Victor E Neuberg</author>
<imprint>
<publisher>OUP</publisher>
<date>1968</date>
</imprint>
</monogr>
</biblStruct>
</listBibl> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.milestoneLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="relation" minOccurs="1"
maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.biblLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.milestoneLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="relation"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listBibl
{
att.global.attributes,
att.sortable.attributes,
att.declarable.attributes,
att.typed.attributes,
(
model.headLike*,
desc*,
( model.milestoneLike | relation | listRelation )*,
( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+
)
}⚓ |
| <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements] | |
| Module | namesdates — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: change handNote licence scriptNote sourceDesc linking: seg msdescription: accMat acquisition additions collation condition custEvent decoNote filiation foliation layout musicNotation origin provenance signatures source summary support surrogates typeNote namesdates: listPerson |
| May contain | namesdates: listPerson listRelation person relation |
| Note | The type attribute may be used to distinguish lists of people of a particular type if convenient. |
| Example | <listPerson type="respondents">
<personGrp xml:id="PXXX"/>
<person xml:id="P1234" sex="2" age="mid"/>
<person xml:id="P4332" sex="1" age="mid"/>
<listRelation>
<relation type="personal" name="spouse"
mutual="#P1234 #P4332"/>
</listRelation>
</listPerson> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation" minOccurs="1"
maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.personLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listPerson"
minOccurs="1" maxOccurs="1"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listPerson
{
att.global.attributes,
att.typed.attributes,
att.declarable.attributes,
att.sortable.attributes,
(
model.headLike*,
desc*,
( relation | listRelation )*,
( ( model.personLike | listPerson )+, ( relation | listRelation )* )+
)
}⚓ |
| <listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places] | |
| Module | namesdates — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: change handNote licence scriptNote sourceDesc linking: seg |
| May contain | |
| Example | <listPlace type="offshoreIslands">
<place>
<placeName>La roche qui pleure</placeName>
</place>
<place>
<placeName>Ile aux cerfs</placeName>
</place>
</listPlace> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation" minOccurs="1"
maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.placeLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listPlace"
minOccurs="1" maxOccurs="1"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listPlace
{
att.global.attributes,
att.typed.attributes,
att.declarable.attributes,
att.sortable.attributes,
(
model.headLike*,
desc*,
( relation | listRelation )*,
( ( model.placeLike | listPlace )+, ( relation | listRelation )* )+
)
}⚓ |
| <listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships] | |
| Module | namesdates — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: add bibl corr del desc head hi item l listBibl note orig p q quote ref reg sic textLang title unclear header: change handNote licence scriptNote sourceDesc linking: seg msdescription: accMat acquisition additions collation condition custEvent decoNote filiation foliation layout musicNotation origin provenance signatures source summary support surrogates typeNote namesdates: listPerson listPlace listRelation |
| May contain | namesdates: listRelation relation |
| Note | May contain a prose description organized as paragraphs, or a sequence of <relation> elements. |
| Example | <listPerson>
<person xml:id="pp1">
<!-- data about person pp1 -->
</person>
<person xml:id="pp2">
<!-- data about person pp1 -->
</person>
<!-- more person (pp3, pp4) elements here -->
<listRelation type="personal">
<relation name="parent"
active="#pp1 #pp2" passive="#pp3 #pp4"/>
<relation name="spouse"
mutual="#pp1 #pp2"/>
</listRelation>
<listRelation type="social">
<relation name="employer" active="#pp1"
passive="#pp3 #pp5 #pp6 #pp7"/>
</listRelation>
</listPerson> The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7. |
| Example | <listPerson>
<person xml:id="en_pp1">
<!-- data about person en_pp1 -->
</person>
<person xml:id="en_pp2">
<!-- data about person en_pp2 -->
</person>
<!-- more person (en_pp3, en_pp4) elements here -->
</listPerson>
<listPlace>
<place xml:id="en_pl1">
<!-- data about place en_pl1 -->
</place>
<!-- more place (en_pl2, en_pl3) elements here -->
</listPlace>
<listRelation>
<relation name="residence"
active="#en_pp1 #en_pp2" passive="#en_pl1"/>
</listRelation> The persons with identifiers en_pp1 and en_pp2 live in en_pl1. |
| Example | <listRelation>
<p>All speakers are members of the Ceruli family, born in Naples.</p>
</listRelation> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
<alternate minOccurs="1" maxOccurs="1">
<classRef key="model.pLike"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="relation"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listRelation
{
att.global.attributes,
att.typed.attributes,
att.sortable.attributes,
( model.headLike*, desc*, ( model.pLike | ( relation | listRelation )+ ) )
}⚓ |
| <locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript] | |||||||||||||||||||
| Module | msdescription — Schema | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout locusGrp material msItem msItemStruct musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||
| May contain | |||||||||||||||||||
| Note | The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example. To associate a <locus> element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone>, <graphic>, or <binaryObject> elements. When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded | ||||||||||||||||||
| Example |
<!-- within ms description --><msItem n="1">
<locus target="#F1r #F1v #F2r" from="1r"
to="2r">ff. 1r-2r</locus>
<author>Ben Jonson</author>
<title>Ode to himself</title>
<rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
<incipit>Com leaue the loathed stage</incipit>
<explicit>And see his chariot triumph ore his wayne.</explicit>
<bibl>
<name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
</msItem>
<!-- within transcription ... -->
<pb xml:id="F1r"/>
<!-- ... -->
<pb xml:id="F1v"/>
<!-- ... -->
<pb xml:id="F2r"/>
<!-- ... --> | ||||||||||||||||||
| Example | The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example: <msItem>
<locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
<title>Birds Praise of Love</title>
<bibl>
<title>IMEV</title>
<biblScope>1506</biblScope>
</bibl>
</msItem> | ||||||||||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.hiLike"/>
</alternate>
</content>
⚓ | ||||||||||||||||||
| Schema Declaration |
element locus
{
att.global.attributes,
att.pointing.attributes,
att.typed.attributes,
attribute scheme { text }?,
attribute from { text }?,
attribute to { text }?,
( text | model.gLike | model.hiLike )*
}⚓ | ||||||||||||||||||
| <locusGrp> (locus group) groups a number of locations which together form a distinct but discontinuous item within a manuscript, manuscript part, or other object. [10.3.5. References to Locations within a Manuscript] | |||||||
| Module | msdescription — Schema | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem msItemStruct musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||
| May contain | msdescription: locus | ||||||
| Example | <msItem>
<locusGrp>
<locus from="13" to="26">Bl. 13--26</locus>
<locus from="37" to="58">37--58</locus>
<locus from="82" to="96">82--96</locus>
</locusGrp>
<note>Stücke von Daniel Ecklin’s Reise ins h. Land</note>
</msItem> | ||||||
| Content model |
<content>
<elementRef key="locus" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ | ||||||
| Schema Declaration |
element locusGrp { att.global.attributes, attribute scheme { text }?, locus+ }⚓ | ||||||
| <mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji — Schema |
| Attributes |
|
| Contained by | gaiji: glyph |
| May contain | gaiji: g character data |
| Note | Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph> element or contain a character that is intended to be the target of this mapping. |
| Example | <mapping type="modern">r</mapping>
<mapping type="standard">人</mapping> |
| Content model |
<content>
<macroRef key="macro.xtext"/>
</content>
⚓ |
| Schema Declaration |
element mapping { att.global.attributes, att.typed.attributes, macro.xtext }⚓ |
| <material> (material) contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type] | |||||||||||||||||
| Module | msdescription — Schema | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||
| Note | The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally. | ||||||||||||||||
| Example | <physDesc>
<p>
<material>Parchment</material> leaves with a
<material>sharkskin</material> binding.</p>
</physDesc> | ||||||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element material
{
att.global.attributes,
att.canonical.attributes,
att.typed.attributes,
attribute function { text }?,
attribute target { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||||||||
| <measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures] | |||||||||
| Module | core — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||
| Example | This example references a definition of a measurement unit declared in the TEI header: <measure type="weight">
<num>2</num> pounds of flesh
</measure>
<measure type="currency">£10-11-6d</measure>
<measure type="area" unitRef="#merk">2 <unit>merks</unit> of old extent</measure>
<!-- In the TEI Header: -->
<encodingDesc>
<unitDecl>
<unitDef xml:id="merk" type="area">
<label>merk</label>
<placeName ref="#Scotland"/>
<desc>A merk was an area of land determined variably by its agricultural
productivity.</desc>
</unitDef>
</unitDecl>
</encodingDesc> | ||||||||
| Example | <measure quantity="40" unit="hogshead"
commodity="rum">2 score hh rum</measure>
<measure quantity="12" unit="count"
commodity="roses">1 doz. roses</measure>
<measure quantity="1" unit="count"
commodity="tulips">a yellow tulip</measure> | ||||||||
| Example | <head>Long papers.</head>
<p>Speakers will be given 30 minutes each: 20 minutes for
presentation, 10 minutes for discussion. Proposals should not
exceed <measure max="500" unit="count"
commodity="words">500
words</measure>. This presentation type is suitable for
substantial research, theoretical or critical discussions.</p> | ||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||
| Schema Declaration |
element measure
{
att.global.attributes,
att.typed.attribute.subtype,
att.measurement.attributes,
att.ranging.attributes,
attribute type { text }?,
macro.phraseSeq
}⚓ | ||||||||
| <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core — Schema |
| Attributes |
|
| Contained by | core: biblStruct |
| May contain | |
| Note | May contain specialized bibliographic elements, in a prescribed order. The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item. |
| Example | <biblStruct>
<analytic>
<author>Chesnutt, David</author>
<title>Historical Editions in the States</title>
</analytic>
<monogr>
<title level="j">Computers and the Humanities</title>
<imprint>
<date when="1991-12">(December, 1991):</date>
</imprint>
<biblScope>25.6</biblScope>
<biblScope unit="page" from="377" to="380">377–380</biblScope>
</monogr>
</biblStruct> |
| Example | <biblStruct type="book">
<monogr>
<author>
<persName>
<forename>Leo Joachim</forename>
<surname>Frachtenberg</surname>
</persName>
</author>
<title type="main" level="m">Lower Umpqua Texts</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Columbia University Press</publisher>
<date>1914</date>
</imprint>
</monogr>
<series>
<title type="main" level="s">Columbia University Contributions to
Anthropology</title>
<biblScope unit="volume">4</biblScope>
</series>
</biblStruct> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0">
<sequence>
<alternate>
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
<elementRef key="title" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.ptrLike"/>
<elementRef key="idno"/>
<elementRef key="textLang"/>
<elementRef key="editor"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<sequence>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="title"/>
<classRef key="model.ptrLike"/>
<elementRef key="idno"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="textLang"/>
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<sequence>
<elementRef key="authority"/>
<elementRef key="idno"/>
</sequence>
</alternate>
<elementRef key="availability"
minOccurs="0" maxOccurs="unbounded"/>
<classRef key="model.noteLike"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0"
maxOccurs="unbounded">
<elementRef key="edition"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="idno"/>
<classRef key="model.ptrLike"/>
<elementRef key="editor"/>
<elementRef key="sponsor"/>
<elementRef key="funder"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<elementRef key="imprint"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="imprint"/>
<elementRef key="extent"/>
<elementRef key="biblScope"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element monogr
{
att.global.attributes,
(
(
(
( author | editor | meeting | respStmt ),
( author | editor | meeting | respStmt )*,
title+,
( model.ptrLike | idno | textLang | editor | respStmt )*
)
| (
( title | model.ptrLike | idno )+,
( textLang | author | editor | meeting | respStmt )*
)
| ( authority, idno )
)?,
availability*,
model.noteLike*,
(
edition,
( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
)*,
imprint,
( imprint | extent | biblScope )*
)
}⚓ |
| <msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | |
| May contain | msdescription: msItem msItemStruct summary |
| Note | Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema. |
| Example | <msContents class="#sermons">
<p>A collection of Lollard sermons</p>
</msContents> |
| Example | <msContents>
<msItem n="1">
<locus>fols. 5r-7v</locus>
<title>An ABC</title>
<bibl>
<title>IMEV</title>
<biblScope>239</biblScope>
</bibl>
</msItem>
<msItem n="2">
<locus>fols. 7v-8v</locus>
<title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>
<bibl>
<title>IMEV</title>
<biblScope>3747</biblScope>
</bibl>
</msItem>
<msItem n="3">
<locus>fol. 8v</locus>
<title>Truth</title>
<bibl>
<title>IMEV</title>
<biblScope>809</biblScope>
</bibl>
</msItem>
<msItem n="4">
<locus>fols. 8v-10v</locus>
<title>Birds Praise of Love</title>
<bibl>
<title>IMEV</title>
<biblScope>1506</biblScope>
</bibl>
</msItem>
<msItem n="5">
<locus>fols. 10v-11v</locus>
<title xml:lang="la">De amico ad amicam</title>
<title xml:lang="la">Responcio</title>
<bibl>
<title>IMEV</title>
<biblScope>16 & 19</biblScope>
</bibl>
</msItem>
<msItem n="6">
<locus>fols. 14r-126v</locus>
<title>Troilus and Criseyde</title>
<note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>
</msItem>
</msContents> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="textLang" minOccurs="0"/>
<elementRef key="titlePage"
minOccurs="0"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msItem"/>
<elementRef key="msItemStruct"/>
</alternate>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element msContents
{
att.global.attributes,
att.msExcerpt.attributes,
att.msClass.attributes,
(
model.pLike+
| ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* )
)
}⚓ |
| <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: add cit corr del desc head hi item l listBibl note orig p q quote ref reg relatedItem sic textLang title unclear header: change handNote licence scriptNote sourceDesc taxonomy linking: seg |
| May contain | msdescription: additional history msContents msFrag msIdentifier msPart physDesc |
| Note | Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable. |
| Example | <msDesc>
<msIdentifier>
<settlement>Oxford</settlement>
<repository>Bodleian Library</repository>
<idno type="Bod">MS Poet. Rawl. D. 169.</idno>
</msIdentifier>
<msContents>
<msItem>
<author>Geoffrey Chaucer</author>
<title>The Canterbury Tales</title>
</msItem>
</msContents>
<physDesc>
<objectDesc>
<p>A parchment codex of 136 folios, measuring approx
28 by 19 inches, and containing 24 quires.</p>
<p>The pages are margined and ruled throughout.</p>
<p>Four hands have been identified in the manuscript: the first 44
folios being written in two cursive anglicana scripts, while the
remainder is for the most part in a mixed secretary hand.</p>
</objectDesc>
</physDesc>
</msDesc> |
| Schematron |
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional">
<sch:let name="gi" value="name(.)"/>
<sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[
name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>.
</sch:report>
</sch:rule> |
| Content model |
<content>
<sequence>
<elementRef key="msIdentifier"/>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msContents"/>
<elementRef key="physDesc"/>
<elementRef key="history"/>
<elementRef key="additional"/>
<elementRef key="msPart"/>
<elementRef key="msFrag"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msDesc
{
att.global.attributes,
att.sortable.attributes,
att.typed.attributes,
att.declaring.attributes,
att.docStatus.attributes,
(
msIdentifier,
model.headLike*,
(
model.pLike+
| ( msContents | physDesc | history | additional | msPart | msFrag )*
)
)
}⚓ |
| <msFrag> (manuscript fragment) contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately [10.11. Manuscript Fragments] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: msDesc |
| May contain | msdescription: additional altIdentifier history msContents msIdentifier physDesc |
| Example | <msDesc>
<msIdentifier>
<msName xml:lang="la">Codex Suprasliensis</msName>
</msIdentifier>
<msFrag>
<msIdentifier>
<settlement>Ljubljana</settlement>
<repository>Narodna in univerzitetna knjiznica</repository>
<idno>MS Kopitar 2</idno>
</msIdentifier>
<msContents>
<summary>Contains ff. 10 to 42 only</summary>
</msContents>
</msFrag>
<msFrag>
<msIdentifier>
<settlement>Warszawa</settlement>
<repository>Biblioteka Narodowa</repository>
<idno>BO 3.201</idno>
</msIdentifier>
</msFrag>
<msFrag>
<msIdentifier>
<settlement>Sankt-Peterburg</settlement>
<repository>Rossiiskaia natsional'naia biblioteka</repository>
<idno>Q.p.I.72</idno>
</msIdentifier>
</msFrag>
</msDesc> |
| Content model |
<content>
<sequence>
<alternate>
<elementRef key="altIdentifier"/>
<elementRef key="msIdentifier"/>
</alternate>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msContents"/>
<elementRef key="physDesc"/>
<elementRef key="history"/>
<elementRef key="additional"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msFrag
{
att.global.attributes,
att.typed.attributes,
(
( altIdentifier | msIdentifier ),
model.headLike*,
( model.pLike+ | ( msContents | physDesc | history | additional )* )
)
}⚓ |
| <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | header: idno msdescription: altIdentifier collection institution msName repository |
| Example | <msIdentifier>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>MS.El.26.C.9</idno>
</msIdentifier> |
| Schematron |
<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier'
or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report> |
| Content model |
<content>
<sequence>
<sequence>
<classRef key="model.placeNamePart"
expand="sequenceOptional"/>
<elementRef key="institution"
minOccurs="0"/>
<elementRef key="repository"
minOccurs="0"/>
<elementRef key="collection"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="idno" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msName"/>
<elementRef key="objectName"/>
<elementRef key="altIdentifier"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msIdentifier
{
att.global.attributes,
(
(
placeName?,
country?,
region?,
settlement?,
district?,
geogName?,
institution?,
repository?,
collection*,
idno*
),
( msName | objectName | altIdentifier )*
)
}⚓ |
| <msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msContents msItem |
| May contain | |
| Example | <msItem class="#saga">
<locus>ff. 1r-24v</locus>
<title>Agrip af Noregs konunga sögum</title>
<incipit>regi oc h<ex>ann</ex> setiho
<gap reason="illegible" extent="7"/>sc
heim se<ex>m</ex> þio</incipit>
<explicit>h<ex>on</ex> hev<ex>er</ex>
<ex>oc</ex>þa buit hesta .ij. aNan viþ
fé enh<ex>on</ex>o<ex>m</ex> aNan til
reiþ<ex>ar</ex>
</explicit>
<textLang mainLang="non">Old Norse/Icelandic</textLang>
</msItem> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="locus"/>
<elementRef key="locusGrp"/>
</alternate>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.titlepagePart"/>
<classRef key="model.msItemPart"/>
<classRef key="model.global"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msItem
{
att.global.attributes,
att.msExcerpt.attributes,
att.msClass.attributes,
(
( locus | locusGrp )*,
(
model.pLike+
| ( model.titlepagePart | model.msItemPart | model.global )+
)
)
}⚓ |
| <msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msContents msItem msItemStruct |
| May contain | |
| Example | <msItemStruct n="2" defective="false"
class="#biblComm">
<locus from="24v" to="97v">24v-97v</locus>
<author>Apringius de Beja</author>
<title type="uniform" xml:lang="la">Tractatus in Apocalypsin</title>
<rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus
in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i
Pacensis eccl<ex>esi</ex>e</rubric>
<finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS
QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S.
DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric>
<bibl>
<ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl>
<textLang mainLang="la">Latin</textLang>
</msItemStruct> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0">
<elementRef key="locus"/>
<elementRef key="locusGrp"/>
</alternate>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<sequence>
<elementRef key="author" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="respStmt"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="rubric" minOccurs="0"/>
<elementRef key="incipit" minOccurs="0"/>
<elementRef key="msItemStruct"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="explicit"
minOccurs="0"/>
<elementRef key="finalRubric"
minOccurs="0"/>
<elementRef key="colophon"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="decoNote"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="listBibl"
minOccurs="0" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="bibl"/>
<elementRef key="biblStruct"/>
</alternate>
<elementRef key="filiation"
minOccurs="0"/>
<classRef key="model.noteLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="textLang"
minOccurs="0"/>
</sequence>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msItemStruct
{
att.global.attributes,
att.msExcerpt.attributes,
att.msClass.attributes,
(
( locus | locusGrp )?,
(
model.pLike+
| (
author*,
respStmt*,
title*,
rubric?,
incipit?,
msItemStruct*,
explicit?,
finalRubric?,
colophon*,
decoNote*,
listBibl*,
( bibl | biblStruct )*,
filiation?,
model.noteLike*,
textLang?
)
)
)
}⚓ |
| <msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: msIdentifier |
| May contain | |
| Example | <msName>The Vercelli Book</msName> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="rs"/>
<elementRef key="name"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element msName
{
att.global.attributes,
att.typed.attributes,
( text | model.gLike | rs | name )*
}⚓ |
| <msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [10.10. Manuscript Parts] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | |
| May contain | msdescription: additional history msContents msIdentifier msPart physDesc |
| Note | As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple <altIdentifier> rather than using the more structured <msIdentifier> element. This usage is however deprecated. |
| Example | <msPart>
<msIdentifier>
<idno>A</idno>
<altIdentifier type="catalog">
<collection>Becker</collection>
<idno>48, Nr. 145</idno>
</altIdentifier>
<altIdentifier type="catalog">
<collection>Wiener Liste</collection>
<idno>4°5</idno>
</altIdentifier>
</msIdentifier>
<head>
<title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>
<origPlace key="tgn_7008085">Weissenburg (?)</origPlace>
<origDate notBefore="0801"
notAfter="0815">IX. Jh., Anfang</origDate>
</head>
</msPart> |
| Example | <msDesc>
<msIdentifier>
<settlement>Amiens</settlement>
<repository>Bibliothèque Municipale</repository>
<idno>MS 3</idno>
<msName>Maurdramnus Bible</msName>
</msIdentifier>
<msContents>
<summary>
<list>
<item xml:lang="en">Miscellany of various texts;</item>
<item xml:lang="la">Prudentius, Psychomachia;</item>
<item xml:lang="la">Physiologus de natura animantium</item>
</list>
</summary>
<textLang mainLang="la">Latin</textLang>
</msContents>
<physDesc>
<objectDesc form="composite_manuscript"/>
</physDesc>
<msPart>
<msIdentifier>
<idno>ms. 10066-77 ff. 140r-156v</idno>
</msIdentifier>
<msContents>
<summary xml:lang="la">Physiologus</summary>
<textLang mainLang="la">Latin</textLang>
</msContents>
</msPart>
<msPart>
<msIdentifier>
<altIdentifier>
<idno>MS 6</idno>
</altIdentifier>
</msIdentifier>
<!-- other information specific to this part here -->
</msPart>
<!-- more parts here -->
</msDesc> |
| Content model |
<content>
<sequence>
<elementRef key="msIdentifier"/>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msContents"/>
<elementRef key="physDesc"/>
<elementRef key="history"/>
<elementRef key="additional"/>
<elementRef key="msPart"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msPart
{
att.global.attributes,
att.typed.attributes,
(
msIdentifier,
model.headLike*,
(
model.pLike+
| ( msContents | physDesc | history | additional | msPart )*
)
)
}⚓ |
| <musicNotation> (music notation) contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <musicNotation>
<p>Square notation of 4-line red staves.</p>
</musicNotation> |
| Example | <musicNotation>Neumes in <term>campo aperto</term> of the St. Gall type.
</musicNotation> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element musicNotation { att.global.attributes, macro.specialPara }⚓ |
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |||||||||||||||||||||
| Module | core — Schema | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp respStmt sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msName musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||||
| Note | Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. | ||||||||||||||||||||
| Example | <name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name> | ||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||||||||||||
| Schema Declaration |
element name
{
att.global.attributes,
att.personal.attributes,
att.datable.attributes,
att.editLike.attributes,
att.typed.attribute.subtype,
attribute type { "person" | "place" | "org" | "unknown" | "other" }?,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||||||||||||
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope biblStruct cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list measure monogr name note num orig p pubPlace publisher q quote ref reg resp respStmt series sic street term textLang title unclear gaiji: glyph header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions adminInfo altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem msItemStruct musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" type="gloss"
resp="#MDMH">
<term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.
<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
<resp>translation from German to English</resp>
<name>Hottinger, Marie Donald Mackie</name>
</respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
| Example | The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note n="126" anchored="true"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element note
{
att.global.attributes,
att.placement.attributes,
att.pointing.attributes,
att.typed.attributes,
att.written.attributes,
att.anchoring.attributes,
macro.specialPara
}⚓ |
| <num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures] | |||||||||||||||||||||||
| Module | core — Schema | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||||||
| Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The <num> element is intended for use in simple applications. | ||||||||||||||||||||||
| Example | <p>I reached <num type="cardinal" value="21">twenty-one</num> on
my <num type="ordinal" value="21">twenty-first</num> birthday</p>
<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
</num> cm per second.</p> | ||||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||||||||||||||
| Schema Declaration |
element num
{
att.global.attributes,
att.typed.attribute.subtype,
att.ranging.attributes,
attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" }?,
attribute value { text }?,
macro.phraseSeq
}⚓ | ||||||||||||||||||||||
| <objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description] | |||||||||
| Module | msdescription — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | msdescription: physDesc | ||||||||
| May contain | core: p msdescription: layoutDesc supportDesc | ||||||||
| Example | <objectDesc form="codex">
<supportDesc material="mixed">
<p>Early modern
<material>parchment</material> and
<material>paper</material>.</p>
</supportDesc>
<layoutDesc>
<layout ruledLines="25 32"/>
</layoutDesc>
</objectDesc> | ||||||||
| Schematron |
<sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#objectdescBook"
context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
<sch:assert test="tei:physDesc/tei:objectDesc[@form]"
role="warn"> The physical form of the carrier should be
recorded in the objectDesc element, with a form attribute.
</sch:assert>
</sch:rule>
<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
<sch:assert test=" tei:physDesc/tei:objectDesc[@form] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc[@form]
"
role="warn"> The
physical form of the carrier should be recorded in the
objectDesc element, with a form attribute, unless it has
been described for the entire manuscript. </sch:assert>
</sch:rule> | ||||||||
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="supportDesc"
minOccurs="0"/>
<elementRef key="layoutDesc"
minOccurs="0"/>
</sequence>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element objectDesc
{
att.global.attributes,
attribute form
{
"codex"
| "roll"
| "sheet"
| "faltbuch"
| "roll-codex"
| "other"
| "unknown"
}?,
( model.pLike+ | ( supportDesc?, layoutDesc? ) )
}⚓ | ||||||||
| <orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp respStmt sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
<placeName key="PEN">Pennsyla.</placeName> Abolition Society
</orgName> [...] | ||||||||||
| Schematron |
<sch:rule context="//tei:msDesc//tei:orgName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'org_\d+')]">In the medieval
catalogue, the orgName element, when a descendant of msDesc,
must have a key matching the pattern 'org_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element orgName
{
att.global.attributes,
att.datable.attributes,
att.editLike.attributes,
att.personal.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone: <l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig>
</l> |
| Example | More usually, an <orig> will be combined with a regularized form within a <choice> element: <l>But this will be a <choice>
<orig>meere</orig>
<reg>mere</reg>
</choice> confusion</l>
<l>And hardly shall we all be <choice>
<orig>vnderstoode</orig>
<reg>understood</reg>
</choice>
</l> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element orig { att.global.attributes, macro.paraContent }⚓ |
| <origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address choice corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <origDate notBefore="-0300"
notAfter="-0200">3rd century BCE</origDate> |
| Schematron |
<sch:rule context="//tei:origDate">
<sch:assert test="@calendar and (@when or @notBefore or @notAfter or @from or @to) and
string-length(normalize-space(string())) gt 0"
role="error"> The origDate element must have two or more
attributes - calendar and at least one of when, notBefore,
notAfter, from and/or to - and must contain some text
describing the date. </sch:assert>
</sch:rule> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element origDate
{
att.global.attributes,
att.datable.attributes,
att.calendarSystem.attributes,
att.dimensions.attributes,
att.editLike.attributes,
att.typed.attributes,
( text | model.gLike | model.phrase | model.global )*
}⚓ |
| <origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing. | ||||||||||
| Example | <origPlace>Birmingham</origPlace> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element origPlace
{
att.global.attributes,
att.naming.attributes,
att.datable.attributes,
att.editLike.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [10.8. History] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: history | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <origin notBefore="1802" notAfter="1845"
evidence="internal" resp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an
old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
</origin> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element origin
{
att.global.attributes,
att.editLike.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.specialPara
}⚓ | ||||||||||
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: availability change editionStmt editorialDecl encodingDesc handNote interpretation langUsage licence projectDesc publicationStmt scriptNote sourceDesc msdescription: accMat acquisition additional additions binding bindingDesc collation condition custEvent custodialHist decoDesc decoNote filiation foliation handDesc history layout layoutDesc msContents msDesc msFrag msItem msItemStruct msPart musicNotation objectDesc origin physDesc provenance recordHist scriptDesc seal sealDesc signatures source summary support supportDesc surrogates typeDesc typeNote namesdates: listRelation person place |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
done?</q>
</p>
<p>
<q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
<q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
<q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p> |
| Schematron |
<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText
|parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q
|parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp
|parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
</sch:report> |
| Schematron |
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText
|parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText.
</sch:report> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element p
{
att.global.attributes,
att.declaring.attributes,
att.fragmentable.attributes,
att.written.attributes,
macro.paraContent
}⚓ |
| <pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | Empty element |
| Note | A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself. The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives. |
| Example | Page numbers may vary in different editions of a text. <p> ... <pb n="145" ed="ed2"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/>
<!-- Page 283 in edition "ed1" starts here--> ... </p> |
| Example | A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body>
<pb n="1" facs="page1.png"/>
<!-- page1.png contains an image of the page;
the text it contains is encoded here -->
<p>
<!-- ... -->
</p>
<pb n="2" facs="page2.png"/>
<!-- similarly, for page 2 -->
<p>
<!-- ... -->
</p>
</body> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element pb
{
att.global.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
}⚓ |
| <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp respStmt sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <persName>
<forename>Edward</forename>
<forename>George</forename>
<surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
<placeName>Knebworth</placeName>
</roleName>
</persName> | ||||||||||
| Schematron |
<sch:rule context="//tei:msDesc//tei:persName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'person_\d+')]">In the
medieval catalogue, the persName element, when a descendant
of msDesc, must have a key matching the pattern
'person_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element persName
{
att.global.attributes,
att.datable.attributes,
att.editLike.attributes,
att.personal.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description] | |||||||||||||||||||||||||||||||||
| Module | namesdates — Schema | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | namesdates: listPerson | ||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||
| Note | May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class. | ||||||||||||||||||||||||||||||||
| Example | <person sex="F" age="adult">
<p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
status B2.</p>
</person> | ||||||||||||||||||||||||||||||||
| Example | <person sex="intersex" role="god"
age="immortal">
<persName>Hermaphroditos</persName>
<persName xml:lang="grc">Ἑρμαφρόδιτος</persName>
</person> | ||||||||||||||||||||||||||||||||
| Example | <person xml:id="Ovi01" sex="M" role="poet">
<persName xml:lang="en">Ovid</persName>
<persName xml:lang="la">Publius Ovidius Naso</persName>
<birth when="-0044-03-20"> 20 March 43 BC <placeName>
<settlement type="city">Sulmona</settlement>
<country key="IT">Italy</country>
</placeName>
</birth>
<death notBefore="0017" notAfter="0018">17 or 18 AD <placeName>
<settlement type="city">Tomis (Constanta)</settlement>
<country key="RO">Romania</country>
</placeName>
</death>
</person> | ||||||||||||||||||||||||||||||||
| Example | The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character. <person xml:id="ariel" gender="U">
<persName>Ariel</persName>
<note>Character in <title level="m">The Tempest</title>.</note>
</person> | ||||||||||||||||||||||||||||||||
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.personPart"/>
<classRef key="model.global"/>
<elementRef key="ptr"/>
</alternate>
</alternate>
</content>
⚓ | ||||||||||||||||||||||||||||||||
| Schema Declaration |
element person
{
att.global.attributes,
att.editLike.attributes,
att.sortable.attributes,
attribute role { list { + } }?,
attribute sex { list { + } }?,
attribute gender { list { + } }?,
attribute age { text }?,
( model.pLike+ | ( model.personPart | model.global | ptr )* )
}⚓ | ||||||||||||||||||||||||||||||||
| <physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | |
| May contain | core: p msdescription: accMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc |
| Example | <physDesc>
<objectDesc form="codex">
<supportDesc material="perg">
<support>Parchment.</support>
<extent>i + 55 leaves
<dimensions scope="all" type="leaf"
unit="inch">
<height>7¼</height>
<width>5⅜</width>
</dimensions>
</extent>
</supportDesc>
<layoutDesc>
<layout columns="2">In double columns.</layout>
</layoutDesc>
</objectDesc>
<handDesc>
<p>Written in more than one hand.</p>
</handDesc>
<decoDesc>
<p>With a few coloured capitals.</p>
</decoDesc>
</physDesc> |
| Content model |
<content>
<sequence>
<classRef key="model.pLike" minOccurs="0"
maxOccurs="unbounded"/>
<classRef key="model.physDescPart"
expand="sequenceOptional"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element physDesc
{
att.global.attributes,
(
model.pLike*,
objectDesc?,
handDesc?,
typeDesc?,
scriptDesc?,
musicNotation?,
decoDesc?,
additions?,
bindingDesc?,
sealDesc?,
accMat?
)
}⚓ |
| <place> (place) contains data about a geographic location [13.3.4. Places] | |
| Module | namesdates — Schema |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <place>
<country>Lithuania</country>
<country xml:lang="lt">Lietuva</country>
<place>
<settlement>Vilnius</settlement>
</place>
<place>
<settlement>Kaunas</settlement>
</place>
</place> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate>
<classRef key="model.pLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.labelLike"/>
<classRef key="model.placeStateLike"/>
<classRef key="model.eventLike"/>
<elementRef key="name"/>
</alternate>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.noteLike"/>
<classRef key="model.biblLike"/>
<elementRef key="idno"/>
<elementRef key="ptr"/>
<elementRef key="linkGrp"/>
<elementRef key="link"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.placeLike"/>
<elementRef key="listPlace"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element place
{
att.global.attributes,
att.typed.attributes,
att.editLike.attributes,
att.sortable.attributes,
(
model.headLike*,
(
model.pLike*
| ( model.labelLike | model.placeStateLike | model.eventLike | name )*
),
( model.noteLike | model.biblLike | idno | ptr | linkGrp | link )*,
( model.placeLike | listPlace )*
)
}⚓ |
| <placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <placeName>
<settlement>Rochester</settlement>
<region>New York</region>
</placeName> | ||||||||||
| Example | <placeName>
<geogName>Arrochar Alps</geogName>
<region>Argylshire</region>
</placeName> | ||||||||||
| Example | <placeName>
<measure>10 miles</measure>
<offset>Northeast of</offset>
<settlement>Attica</settlement>
</placeName> | ||||||||||
| Schematron |
<sch:rule context="//tei:msDesc//tei:placeName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the placeName element, when a descendant of
msDesc, must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element placeName
{
att.datable.attributes,
att.editLike.attributes,
att.global.attributes,
att.personal.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: address |
| May contain | Character data only |
| Note | The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used. |
| Example | <postCode>HR1 3LR</postCode> |
| Example | <postCode>60142-7</postCode> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element postCode { att.global.attributes, text }⚓ |
| <principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement] | |||||||||||
| Module | header — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element principal
{
att.global.attributes,
att.canonical.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq.limited
}⚓ | ||||||||||
| <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | |
| Note | Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts. |
| Example | <profileDesc>
<langUsage>
<language ident="fr">French</language>
</langUsage>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc>
<settingDesc>
<setting>
<name>Paris, France</name>
<time>Late 19th century</time>
</setting>
</settingDesc>
</profileDesc> |
| Content model |
<content>
<classRef key="model.profileDescPart"
minOccurs="0" maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element profileDesc { att.global.attributes, model.profileDescPart* }⚓ |
| <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Example | <projectDesc>
<p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
</projectDesc> |
| Content model |
<content>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element projectDesc
{
att.global.attributes,
att.declarable.attributes,
model.pLike+
}⚓ |
| <provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: history | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <provenance>Listed as the property of Lawrence Sterne in 1788.</provenance>
<provenance>Sold at Sothebys in 1899.</provenance> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element provenance
{
att.global.attributes,
att.datable.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
macro.specialPara
}⚓ | ||||||||||
| <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <publicationStmt>
<publisher>Oxford University Press</publisher>
<pubPlace>Oxford</pubPlace>
<date>1989</date>
</publicationStmt> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element pubPlace
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq
}⚓ |
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Note | Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
| Example | <publicationStmt>
<publisher>C. Muquardt </publisher>
<pubPlace>Bruxelles & Leipzig</pubPlace>
<date when="1846"/>
</publicationStmt> |
| Example | <publicationStmt>
<publisher>Chadwyck Healey</publisher>
<pubPlace>Cambridge</pubPlace>
<availability>
<p>Available under licence only</p>
</availability>
<date when="1992">1992</date>
</publicationStmt> |
| Example | <publicationStmt>
<publisher>Zea Books</publisher>
<pubPlace>Lincoln, NE</pubPlace>
<date>2017</date>
<availability>
<p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
</availability>
<ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt> |
| Content model |
<content>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.publicationStmtPart.agency"/>
<classRef key="model.publicationStmtPart.detail"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element publicationStmt
{
att.global.attributes,
(
( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+
| model.pLike+
)
}⚓ |
| <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
| Example | <imprint>
<pubPlace>Oxford</pubPlace>
<publisher>Clarendon Press</publisher>
<date>1987</date>
</imprint> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element publisher
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq
}⚓ |
| <q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation] | |||||||||
| Module | core — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope cit citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout locus material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||
| Note | May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks. | ||||||||
| Example | It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q> | ||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||
| Schema Declaration |
element q
{
att.global.attributes,
att.ascribed.directed.attributes,
attribute type
{
"spoken"
| "thought"
| "written"
| "soCalled"
| "foreign"
| "distinct"
| "term"
| "emph"
| "mentioned"
}?,
macro.specialPara
}⚓ | ||||||||
| <recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [10.9.1. Administrative Information] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: adminInfo |
| May contain | |
| Example | <recordHist>
<source>
<p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research
by P.M.W.Robinson</p>
</source>
<change when="1999-06-23">
<name>LDB</name> (editor)
checked examples against DTD version 3.6
</change>
</recordHist> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="source"/>
<elementRef key="change" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element recordHist
{
att.global.attributes,
( model.pLike+ | ( source, change* ) )
}⚓ |
| <reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone: <q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
</q> |
| Example | It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings: <q>Please <choice>
<reg resp="#LB">knock</reg>
<orig>cnk</orig>
</choice> if an <choice>
<reg>answer</reg>
<orig>nsr</orig>
</choice> is <choice>
<reg>required</reg>
<orig>reqd</orig>
</choice>
</q> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element reg
{
att.global.attributes,
att.editLike.attributes,
att.typed.attributes,
macro.paraContent
}⚓ |
| <region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <placeName>
<region type="state" n="IL">Illinois</region>
</placeName> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element region
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships] | |||||||||||||||||||||||||||||||||||
| Module | namesdates — Schema | ||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||
| Contained by | core: listBibl namesdates: listPerson listPlace listRelation | ||||||||||||||||||||||||||||||||||
| May contain | core: desc | ||||||||||||||||||||||||||||||||||
| Note | Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages. | ||||||||||||||||||||||||||||||||||
| Example | <relation type="social" name="supervisor"
active="#p1" passive="#p2 #p3 #p4"/> This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4. | ||||||||||||||||||||||||||||||||||
| Example | <relation type="personal" name="friends"
mutual="#p2 #p3 #p4"/> This indicates that p2, p3, and p4 are all friends. | ||||||||||||||||||||||||||||||||||
| Example | <relation type="CRM"
name="P89_falls_within"
active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"
passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/> This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs. | ||||||||||||||||||||||||||||||||||
| Example | <relation resp="http://viaf.org/viaf/44335536/"
ref="http://purl.org/saws/ontology#isVariantOf"
active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"
passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/> This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs). | ||||||||||||||||||||||||||||||||||
| Schematron |
<sch:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</sch:assert> | ||||||||||||||||||||||||||||||||||
| Schematron |
<sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report> | ||||||||||||||||||||||||||||||||||
| Schematron |
<sch:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</sch:report> | ||||||||||||||||||||||||||||||||||
| Content model |
<content>
<elementRef key="desc" minOccurs="0"/>
</content>
⚓ | ||||||||||||||||||||||||||||||||||
| Schema Declaration |
element relation
{
att.global.attributes,
att.datable.attributes,
att.editLike.attributes,
att.canonical.attributes,
att.sortable.attributes,
att.typed.attributes,
attribute calendar { list { + } }?,
attribute name { text }?,
( attribute active { list { + } }? | attribute mutual { list { + } }? ),
attribute passive { list { + } }?,
desc?
}⚓ | ||||||||||||||||||||||||||||||||||
| <repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: altIdentifier msIdentifier |
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <msIdentifier>
<settlement>Oxford</settlement>
<institution>University of Oxford</institution>
<repository>Bodleian Library</repository>
<idno>MS. Bodley 406</idno>
</msIdentifier> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element repository
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq.limited
}⚓ |
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |||||||||||
| Module | core — Schema | ||||||||||
| Attributes |
| ||||||||||
| Contained by | core: respStmt | ||||||||||
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. | ||||||||||
| Example | <respStmt>
<resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
<name>Edward Child</name>
</respStmt> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element resp
{
att.global.attributes,
att.canonical.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq.limited
}⚓ | ||||||||||
| <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: editionStmt titleStmt msdescription: msItem msItemStruct |
| May contain | |
| Example | <respStmt>
<resp>transcribed from original ms</resp>
<persName>Claus Huitfeldt</persName>
</respStmt> |
| Example | <respStmt>
<resp>converted to XML encoding</resp>
<name>Alan Morrison</name>
</respStmt> |
| Content model |
<content>
<sequence>
<alternate>
<sequence>
<elementRef key="resp" minOccurs="1"
maxOccurs="unbounded"/>
<classRef key="model.nameLike.agent"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
<sequence>
<classRef key="model.nameLike.agent"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="resp" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
<elementRef key="note" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element respStmt
{
att.global.attributes,
att.canonical.attributes,
(
( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
note*
)
}⚓ |
| <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | |
| Note | If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list. |
| Example | <revisionDesc status="embargoed">
<change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
</revisionDesc> |
| Content model |
<content>
<alternate>
<elementRef key="list" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="listChange"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="change" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element revisionDesc
{
att.global.attributes,
att.docStatus.attributes,
( list+ | listChange+ | change+ )
}⚓ |
| <row> (row) contains one row of a table. [14.1.1. TEI Tables] | |
| Module | figures — Schema |
| Attributes |
|
| Contained by | figures: table |
| May contain | figures: cell |
| Example | <row role="data">
<cell role="label">Classics</cell>
<cell>Idle listless and unimproving</cell>
</row> |
| Content model |
<content>
<elementRef key="cell" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }⚓ |
| <rubric> (rubric) contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript or other object signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, typically in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msItem msItemStruct |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
<rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric>
<rubric>
<locus>16. f. 28v in margin: </locus>Dicta Cassiodori
</rubric> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element rubric
{
att.global.attributes,
att.typed.attributes,
att.msExcerpt.attributes,
macro.phraseSeq
}⚓ |
| <scriptDesc> (script description) contains a description of the scripts used in a manuscript or other object. [10.7.2.1. Writing] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <scriptDesc>
<p/>
</scriptDesc> |
| Example | <scriptDesc>
<summary>Contains two distinct styles of scripts </summary>
<scriptNote xml:id="style-1">.</scriptNote>
<scriptNote xml:id="style-2">.</scriptNote>
</scriptDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="scriptNote"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element scriptDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, scriptNote+ ) )
}⚓ |
| <seal> (seal) contains a description of one seal or similar applied to the object described [10.7.3.2. Seals] | |||||||||||||||||
| Module | msdescription — Schema | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Contained by | msdescription: sealDesc | ||||||||||||||||
| May contain | |||||||||||||||||
| Example | <seal n="2" type="pendant"
subtype="cauda_duplex">
<p>The seal of <name>Jens Olufsen</name> in black wax.
(<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.
Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p>
</seal> | ||||||||||||||||
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<elementRef key="decoNote"/>
</alternate>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element seal
{
att.global.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
attribute contemporary { text }?,
( model.pLike | decoNote )+
}⚓ | ||||||||||||||||
| <sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of <seal> elements. [10.7.3.2. Seals] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <sealDesc>
<seal type="pendant" contemporary="true">
<p>Green wax vertical oval seal attached at base.</p>
</seal>
</sealDesc> |
| Example | <sealDesc>
<p>Parchment strip for seal in place; seal missing.</p>
</sealDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="decoNote"/>
<elementRef key="seal"/>
<elementRef key="condition"/>
</alternate>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element sealDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, ( decoNote | seal | condition )+ ) )
}⚓ |
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |
| Module | linking — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element. |
| Example | <seg>When are you leaving?</seg>
<seg>Tomorrow.</seg> |
| Example | <s>
<seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield.
</s> |
| Example | <seg type="preamble">
<seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
<seg>Sinfiotli was the eldest of his sons ...</seg>
<seg>Borghild, Sigmund's wife, had a brother ... </seg>
</seg> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element seg
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
att.written.attributes,
att.notated.attributes,
macro.paraContent
}⚓ |
| <series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: bibl biblStruct |
| May contain | |
| Example | <series xml:lang="de">
<title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
<respStmt>
<resp>Herausgegeben von</resp>
<name type="person">Manfred Thaller</name>
<name type="org">Max-Planck-Institut für Geschichte</name>
</respStmt>
<title level="s">Serie A: Historische Quellenkunden</title>
<biblScope>Band 11</biblScope>
</series> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="title"/>
<classRef key="model.ptrLike"/>
<elementRef key="editor"/>
<elementRef key="respStmt"/>
<elementRef key="biblScope"/>
<elementRef key="idno"/>
<elementRef key="textLang"/>
<classRef key="model.global"/>
<elementRef key="availability"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element series
{
att.global.attributes,
(
text
| model.gLike
| title
| model.ptrLike
| editor
| respStmt
| biblScope
| idno
| textLang
| model.global
| availability
)*
}⚓ |
| <settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names] | |||||||||||
| Module | namesdates — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions altIdentifier catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msIdentifier musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <placeName>
<settlement type="town">Glasgow</settlement>
<region>Scotland</region>
</placeName> | ||||||||||
| Schematron |
<sch:rule context="//tei:origin//tei:settlement[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the settlement element, when a descendant of
origin, must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule> | ||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element settlement
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields. |
| Example | If all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone: I don't know, Juan. It's so far in the past now
— how <sic>we can</sic> prove or disprove anyone's theories? |
| Example | It is also possible, using the <choice> and <corr> elements, to provide a corrected reading: I don't know, Juan. It's so far in the past now
— how <choice>
<sic>we can</sic>
<corr>can we</corr>
</choice> prove or disprove anyone's theories? |
| Example | for his nose was as sharp as
a pen, and <choice>
<sic>a Table</sic>
<corr>a' babbld</corr>
</choice> of green fields. |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element sic { att.global.attributes, macro.paraContent }⚓ |
| <signatures> (signatures) contains discussion of the leaf or quire signatures found within a codex or similar object. [10.3.7. Catchwords, Signatures, Secundo Folio] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <signatures>Quire and leaf signatures in letters, [b]-v, and roman
numerals; those in quires 10 (1) and 17 (s) in red ink and different
from others; every third quire also signed with red crayon in arabic
numerals in the center lower margin of the first leaf recto: "2" for
quire 4 (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for
quire 10 (f. 65), "5," in a later hand, for quire 13 (f. 89), "6," in
a later hand, for quire 16 (f. 113).</signatures> |
| Schematron |
<sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element signatures
{
att.typed.attributes,
att.global.attributes,
macro.specialPara
}⚓ |
| <source> (source) describes the original source for the information contained with a manuscript or object description. [10.9.1.1. Record History] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: recordHist |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <source>Derived from <ref>Stanley (1960)</ref>
</source> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element source { att.global.attributes, macro.specialPara }⚓ |
| <sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | core: bibl biblStruct list listBibl p figures: table msdescription: msDesc namesdates: listPerson listPlace listRelation |
| Example | <sourceDesc>
<bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>. </bibl>
</sourceDesc> |
| Example | <sourceDesc>
<p>Born digital: no previous source exists.</p>
</sourceDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.biblLike"/>
<classRef key="model.sourceDescPart"/>
<classRef key="model.listLike"/>
</alternate>
</alternate>
</content>
⚓ |
| Schema Declaration |
element sourceDesc
{
att.global.attributes,
att.declarable.attributes,
(
model.pLike+
| ( model.biblLike | model.sourceDescPart | model.listLike )+
)
}⚓ |
| <sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement] | |||||||||||
| Module | header — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title figures: figure header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Note | Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility. | ||||||||||
| Example | <sponsor>Association for Computers and the Humanities</sponsor>
<sponsor>Association for Computational Linguistics</sponsor>
<sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element sponsor
{
att.global.attributes,
att.canonical.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq.limited
}⚓ | ||||||||||
| <stamp> (stamp) contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps] | |||||||||||
| Module | msdescription — Schema | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine author biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||
| Example | <rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
SI NON LICET<lb/>
NOBIS RO<lb/>
manii imperii <stamp>Bodleian stamp</stamp>
<lb/>
</rubric> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element stamp
{
att.global.attributes,
att.typed.attributes,
att.datable.attributes,
attribute calendar { list { + } }?,
macro.phraseSeq
}⚓ | ||||||||||
| <street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: address |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned. |
| Example | <street>via della Faggiola, 36</street> |
| Example | <street>
<name>Duntaggin</name>, 110 Southmoor Road
</street> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element street { att.global.attributes, macro.phraseSeq }⚓ |
| <subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions] | |
| Module | transcr — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | |
| Example | ... are all included. <del hand="#RG">It is</del>
<subst>
<add>T</add>
<del>t</del>
</subst>he expressed
|
| Example | that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
<del>very</del>
<lb/>
<add>principally</add>
</subst> remembered in her Will.
|
| Example | <ab>τ<subst>
<add place="above">ῶν</add>
<del>α</del>
</subst>
συνκυρόντ<subst>
<add place="above">ων</add>
<del>α</del>
</subst>
ἐργαστηρί<subst>
<add place="above">ων</add>
<del>α</del>
</subst>
</ab> |
| Example | <subst>
<del>
<gap reason="illegible" quantity="5"
unit="character"/>
</del>
<add>apple</add>
</subst> |
| Schematron |
<sch:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">
<sch:name/> must have at least one child add and at least one child del or surplus</sch:assert> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="add"/>
<elementRef key="surplus"/>
<elementRef key="del"/>
<classRef key="model.milestoneLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element subst
{
att.global.attributes,
att.transcriptional.attributes,
att.dimensions.attributes,
( add | surplus | del | model.milestoneLike )+
}⚓ |
| <summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: decoDesc handDesc history layoutDesc msContents scriptDesc sealDesc typeDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <summary>This item consists of three books with a prologue and an epilogue.
</summary> |
| Example | <typeDesc>
<summary>Uses a mixture of Roman and Black Letter types.</summary>
<typeNote>Antiqua typeface, showing influence of Jenson's Venetian
fonts.</typeNote>
<typeNote>The black letter face is a variant of Schwabacher.</typeNote>
</typeDesc> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element summary { att.global.attributes, macro.specialPara }⚓ |
| <supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |||||||
| Module | transcr — Schema | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||
| Note | The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. | ||||||
| Example | I am dr Sr yr
<supplied reason="illegible"
source="#amanuensis_copy">very humble Servt</supplied>
Sydney Smith | ||||||
| Example | <supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar | ||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||
| Schema Declaration |
element supplied
{
att.global.attributes,
att.editLike.attributes,
att.dimensions.attributes,
attribute reason { list { + } }?,
macro.paraContent
}⚓ | ||||||
| <support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <objectDesc form="roll">
<supportDesc>
<support> Parchment roll with <material>silk</material> ribbons.
</support>
</supportDesc>
</objectDesc> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element support { att.global.attributes, macro.specialPara }⚓ |
| <supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description] | |||||||||
| Module | msdescription — Schema | ||||||||
| Attributes |
| ||||||||
| Contained by | msdescription: objectDesc | ||||||||
| May contain | |||||||||
| Example | <supportDesc>
<support> Parchment roll with <material>silk</material> ribbons.
</support>
</supportDesc> | ||||||||
| Schematron |
<sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#supportdesc"
context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
<sch:assert test="tei:physDesc/tei:objectDesc/tei:supportDesc[@material]"
role="warn"> The material (parchment, paper, etc.) of a
manuscript should be recorded in the supportDesc element,
with a material attribute. </sch:assert>
</sch:rule>
<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
<sch:assert test=" tei:physDesc/tei:objectDesc/tei:supportDesc[@material] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc[@material]
"
role="warn"> The
material (parchment, paper, etc.) of each part should be
recorded in the supportDesc element, with a material
attribute, unless it has been described for the entire
manuscript. </sch:assert>
</sch:rule> | ||||||||
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="support" minOccurs="0"/>
<elementRef key="extent" minOccurs="0"/>
<elementRef key="foliation"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="collation"
minOccurs="0"/>
<elementRef key="condition"
minOccurs="0"/>
</sequence>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element supportDesc
{
att.global.attributes,
attribute material
{
"perg" | "chart" | "papyrus" | "palm" | "mixed" | "other" | "unknown"
}?,
( model.pLike+ | ( support?, extent?, foliation*, collation?, condition? ) )
}⚓ | ||||||||
| <surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||||||||
| Module | transcr — Schema | ||||||||||||||
| Attributes |
| ||||||||||||||
| Contained by | transcr: facsimile surface surfaceGrp zone | ||||||||||||||
| May contain | |||||||||||||||
| Note | The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc. The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high. The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid. Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> element. | ||||||||||||||
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="200" lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
</facsimile> | ||||||||||||||
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.labelLike"/>
<classRef key="model.graphicLike"/>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<alternate>
<elementRef key="zone"/>
<elementRef key="line"/>
<elementRef key="path"/>
<elementRef key="surface"/>
<elementRef key="surfaceGrp"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ | ||||||||||||||
| Schema Declaration |
element surface
{
att.global.attributes,
att.coordinated.attributes,
att.declaring.attributes,
att.typed.attributes,
attribute attachment { text }?,
attribute flipping { text }?,
(
( model.global | model.labelLike | model.graphicLike )*,
( ( zone | line | path | surface | surfaceGrp ), model.global* )*
)
}⚓ | ||||||||||||||
| <surfaceGrp> (surface group) defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles] | |
| Module | transcr — Schema |
| Attributes |
|
| Contained by | transcr: facsimile surface surfaceGrp |
| May contain | |
| Note | Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements. |
| Example | <sourceDoc>
<surfaceGrp>
<surface ulx="0" uly="0" lrx="200"
lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
<surface ulx="0" uly="0" lrx="200"
lry="300">
<graphic url="Bovelles-49v.png"/>
</surface>
</surfaceGrp>
</sourceDoc> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.global"/>
<elementRef key="surface"/>
<elementRef key="surfaceGrp"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element surfaceGrp
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
( model.global | surface | surfaceGrp )+
}⚓ |
| <surrogates> (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [10.9. Additional Information] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: additional |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <surrogates>
<bibl>
<title type="gmd">diapositive</title>
<idno>AM 74 a, fol.</idno>
<date>May 1984</date>
</bibl>
<bibl>
<title type="gmd">b/w prints</title>
<idno>AM 75 a, fol.</idno>
<date>1972</date>
</bibl>
</surrogates> |
| Schematron |
<sch:rule context="//tei:surrogates/tei:bibl">
<sch:report test="contains(@type, 'fascimile')"
role="warn"> The
type attribute of "<sch:value-of select="@type"/>" contains
a typo (fascimile should be facsimile). </sch:report>
</sch:rule> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element surrogates { att.global.attributes, macro.specialPara }⚓ |
| <table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables] | |||||||||||||||||
| Module | figures — Schema | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | header: change handNote licence scriptNote sourceDesc linking: seg | ||||||||||||||||
| May contain | |||||||||||||||||
| Note | Contains an optional heading and a series of rows. Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate. | ||||||||||||||||
| Example | <table rows="4" cols="4">
<head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
<row role="label">
<cell role="data"/>
<cell role="data">Dossing Cribs or Lodging Houses</cell>
<cell role="data">Beds</cell>
<cell role="data">Needys or Nightly Lodgers</cell>
</row>
<row role="data">
<cell role="label">Bury St Edmund's</cell>
<cell role="data">5</cell>
<cell role="data">8</cell>
<cell role="data">128</cell>
</row>
<row role="data">
<cell role="label">Thetford</cell>
<cell role="data">3</cell>
<cell role="data">6</cell>
<cell role="data">36</cell>
</row>
<row role="data">
<cell role="label">Attleboro'</cell>
<cell role="data">3</cell>
<cell role="data">5</cell>
<cell role="data">20</cell>
</row>
<row role="data">
<cell role="label">Wymondham</cell>
<cell role="data">1</cell>
<cell role="data">11</cell>
<cell role="data">22</cell>
</row>
</table> | ||||||||||||||||
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.headLike"/>
<classRef key="model.global"/>
</alternate>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="row"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.graphicLike"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element table
{
att.global.attributes,
att.typed.attributes,
attribute rows { text }?,
attribute cols { text }?,
(
( model.headLike | model.global )*,
( ( row, model.global* )+ | ( model.graphicLike, model.global* )+ ),
( model.divBottom, model.global* )*
)
}⚓ | ||||||||||||||||
| <taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | |
| May contain | |
| Note | Nested taxonomies are common in many fields, so the <taxonomy> element can be nested. |
| Example | <taxonomy xml:id="tax.b">
<bibl>Brown Corpus</bibl>
<category xml:id="tax.b.a">
<catDesc>Press Reportage</catDesc>
<category xml:id="tax.b.a1">
<catDesc>Daily</catDesc>
</category>
<category xml:id="tax.b.a2">
<catDesc>Sunday</catDesc>
</category>
<category xml:id="tax.b.a3">
<catDesc>National</catDesc>
</category>
<category xml:id="tax.b.a4">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="tax.b.a5">
<catDesc>Political</catDesc>
</category>
<category xml:id="tax.b.a6">
<catDesc>Sports</catDesc>
</category>
</category>
<category xml:id="tax.b.d">
<catDesc>Religion</catDesc>
<category xml:id="tax.b.d1">
<catDesc>Books</catDesc>
</category>
<category xml:id="tax.b.d2">
<catDesc>Periodicals and tracts</catDesc>
</category>
</category>
</taxonomy> |
| Example | <taxonomy>
<category xml:id="literature">
<catDesc>Literature</catDesc>
<category xml:id="poetry">
<catDesc>Poetry</catDesc>
<category xml:id="sonnet">
<catDesc>Sonnet</catDesc>
<category xml:id="shakesSonnet">
<catDesc>Shakespearean Sonnet</catDesc>
</category>
<category xml:id="petraSonnet">
<catDesc>Petrarchan Sonnet</catDesc>
</category>
</category>
<category xml:id="haiku">
<catDesc>Haiku</catDesc>
</category>
</category>
<category xml:id="drama">
<catDesc>Drama</catDesc>
</category>
</category>
<category xml:id="meter">
<catDesc>Metrical Categories</catDesc>
<category xml:id="feet">
<catDesc>Metrical Feet</catDesc>
<category xml:id="iambic">
<catDesc>Iambic</catDesc>
</category>
<category xml:id="trochaic">
<catDesc>trochaic</catDesc>
</category>
</category>
<category xml:id="feetNumber">
<catDesc>Number of feet</catDesc>
<category xml:id="pentameter">
<catDesc>>Pentameter</catDesc>
</category>
<category xml:id="tetrameter">
<catDesc>>Tetrameter</catDesc>
</category>
</category>
</category>
</taxonomy>
<!-- elsewhere in document -->
<lg ana="#shakesSonnet #iambic #pentameter">
<l>Shall I compare thee to a summer's day</l>
<!-- ... -->
</lg> |
| Content model |
<content>
<alternate>
<alternate>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
<sequence>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.descLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="equiv" minOccurs="1"
maxOccurs="1"/>
<elementRef key="gloss" minOccurs="1"
maxOccurs="1"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
</sequence>
</alternate>
<sequence>
<classRef key="model.biblLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element taxonomy
{
att.global.attributes,
att.datcat.attributes,
(
(
( category | taxonomy )+
| ( ( model.descLike | equiv | gloss )+, ( category | taxonomy )* )
)
| ( model.biblLike, ( category | taxonomy )* )
)
}⚓ |
| <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | textstructure: TEI |
| May contain | derived-module-msdesc: include header: encodingDesc fileDesc profileDesc revisionDesc |
| Note | One of the few elements unconditionally required in any TEI document. |
| Example | <teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader> |
| Content model |
<content>
<sequence>
<elementRef key="fileDesc"/>
<classRef key="model.teiHeaderPart"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="revisionDesc"
minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element teiHeader
{
att.global.attributes,
( fileDesc, model.teiHeaderPart*, revisionDesc? )
}⚓ |
| <term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses] | |
| Module | core — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote keywords language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName orgName persName placeName region settlement surname tagdocs: gi character data |
| Note | When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute. In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release. |
| Example | A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers. |
| Example | We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss> |
| Example | We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss> |
| Example | We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below. |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element term
{
att.global.attributes,
att.declaring.attributes,
att.pointing.attributes,
att.typed.attributes,
att.canonical.attributes,
att.sortable.attributes,
att.cReferencing.attributes,
macro.phraseSeq
}⚓ |
| <text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text] | |
| Module | textstructure — Schema |
| Attributes |
|
| Member of | |
| Contained by | textstructure: TEI |
| May contain | |
| Note | This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose. |
| Example | <text>
<front>
<docTitle>
<titlePart>Autumn Haze</titlePart>
</docTitle>
</front>
<body>
<l>Is it a dragonfly or a maple leaf</l>
<l>That settles softly down upon the water?</l>
</body>
</text> |
| Example | The body of a text may be replaced by a group of nested texts, as in the following schematic: <text>
<front>
<!-- front matter for the whole group -->
</front>
<group>
<text>
<!-- first text -->
</text>
<text>
<!-- second text -->
</text>
</group>
</text> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<elementRef key="front"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<alternate>
<elementRef key="body"/>
<elementRef key="group"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<elementRef key="back"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element text
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
att.written.attributes,
(
model.global*,
( front, model.global* )?,
( body | group ),
model.global*,
( back, model.global* )?
)
}⚓ |
| <textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification] | |
| Module | header — Schema |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | header: keywords |
| Example | <taxonomy>
<category xml:id="acprose">
<catDesc>Academic prose</catDesc>
</category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
<catRef target="#acprose"/>
<classCode scheme="http://www.udcc.org">001.9</classCode>
<keywords scheme="http://authorities.loc.gov">
<list>
<item>End of the world</item>
<item>History - philosophy</item>
</list>
</keywords>
</textClass> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="classCode"/>
<elementRef key="catRef"/>
<elementRef key="keywords"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element textClass
{
att.global.attributes,
att.declarable.attributes,
( classCode | catRef | keywords )*
}⚓ |
| <textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems] | |||||||||||||
| Module | core — Schema | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | msdescription: msContents msItem msItemStruct | ||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||
| Note | This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description. In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header. | ||||||||||||
| Example | <textLang mainLang="en" otherLangs="la"> Predominantly in English with Latin
glosses</textLang> | ||||||||||||
| Schematron |
<sch:rule context="//tei:msItem">
<sch:assert test=" tei:textLang or ancestor::tei:msContents/tei:textLang or ancestor::tei:msItem/tei:textLang
or ( tei:msItem and (every $i in tei:msItem satisfies $i/descendant-or-self::tei:textLang)
) "
role="warn"> The
language of each item should be recorded in a textLang
element, unless it has been described for the entire
manuscript or part. Use 'und' for undetermined or 'zxx' if
there is no linguistic content. </sch:assert>
</sch:rule>
<sch:rule context="//tei:textLang">
<sch:assert test="@mainLang and string-length(normalize-space(string())) gt 0"
role="error"> The predominant language must be recorded in
using a code in a mainLang attribute (and an otherLang
attribute if there are other languages) and described as
text within the textLang element. </sch:assert>
</sch:rule>
<sch:rule context="//tei:textLang/@mainLang | //tei:textLang/@otherLangs | //@xml:lang">
<sch:assert test="every $code in tokenize(., ' ') satisfies matches($code, '^[a-z]{2,3}(-|$)')"
role="error"> Codes in <sch:value-of select="name(.)"/>
attributes must conform to BCP 47
(https://tools.ietf.org/html/bcp47), starting with an ISO
639 code for the language, then optionally further codes for
the script (ISO 15924), region, transliteration, etc.
</sch:assert>
</sch:rule> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element textLang
{
att.global.attributes,
attribute mainLang { text }?,
attribute otherLangs { list { * } }?,
macro.specialPara
}⚓ | ||||||||||||
| <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||||||||||||
| Module | core — Schema | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | core: abbr add addrLine analytic author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure monogr name note num orig p pubPlace publisher q quote ref reg resp series sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor titleStmt linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem msItemStruct musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||||||||||||||||
| Note | The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title. | ||||||||||||||||||||||||||||||||
| Example | <title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title> | ||||||||||||||||||||||||||||||||
| Example | <title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title> | ||||||||||||||||||||||||||||||||
| Example | <title type="full">
<title type="main">Synthèse</title>
<title type="sub">an international journal for
epistemology, methodology and history of
science</title>
</title> | ||||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule> | ||||||||||||||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||||||||||||||||||||||||||||
| Schema Declaration |
element title
{
att.global.attributes,
att.typed.attribute.subtype,
att.canonical.attributes,
att.datable.attributes,
attribute type { "main" | "sub" | "alt" | "short" | "desc" | "collection" }?,
attribute calendar { list { + } }?,
attribute level { "a" | "m" | "j" | "s" | "u" }?,
macro.paraContent
}⚓ | ||||||||||||||||||||||||||||||||
| <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
| Module | header — Schema |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <titleStmt>
<title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
<respStmt>
<resp>compiled by</resp>
<name>P.J. Lucas</name>
</respStmt>
</titleStmt> |
| Content model |
<content>
<sequence>
<elementRef key="title" minOccurs="1"
maxOccurs="unbounded"/>
<classRef key="model.respLike"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element titleStmt { att.global.attributes, ( title+, model.respLike* ) }⚓ |
| <typeDesc> (typeface description) contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [10.7.2.1. Writing] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <typeDesc>
<p>Uses an unidentified black letter font, probably from the
15th century</p>
</typeDesc> |
| Example | <typeDesc>
<summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
<typeNote xml:id="Frak1">Blackletter face, showing
similarities to those produced in Wuerzburg after 1470.</typeNote>
<typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
</typeDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="typeNote" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element typeDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, typeNote+ ) )
}⚓ |
| <typeNote> (typographic note) describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription — Schema |
| Attributes |
|
| Contained by | msdescription: typeDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data |
| Example | <typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence.
</typeNote> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element typeNote
{
att.global.attributes,
att.handFeatures.attributes,
macro.specialPara
}⚓ |
| <unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||||||
| Module | core — Schema | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del editor email expan foreign head hi item l label lg measure name note num orig p pubPlace publisher q quote ref reg sic street term textLang title unclear figures: cell header: change distributor edition extent handNote licence scriptNote linking: seg msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark | ||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear gaiji: g header: idno linking: seg msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName country district forename geo geogFeat geogName listPerson listPlace listRelation orgName persName placeName region settlement surname tagdocs: gi character data | ||||||||||||||||||||
| Note | The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility. The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands. | ||||||||||||||||||||
| Example | <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u> | ||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||||||||||||||||
| Schema Declaration |
element unclear
{
att.global.attributes,
att.editLike.attributes,
att.dimensions.attributes,
attribute reason
{
list
{
(
"illegible"
| "inaudible"
| "faded"
| "background_noise"
| "eccentric_ductus"
)+
}
}?,
attribute agent { text }?,
macro.paraContent
}⚓ | ||||||||||||||||||||
| <width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions] | |
| Module | msdescription — Schema |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp sic street term textLang title unclear header: authority catDesc change distributor edition extent funder handNote language licence principal scriptNote sponsor linking: seg msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote dimensions explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark |
| May contain | gaiji: g character data |
| Note | If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis. |
| Example | <width unit="in">4</width> |
| Content model |
<content>
<macroRef key="macro.xtext"/>
</content>
⚓ |
| Schema Declaration |
element width { att.global.attributes, att.dimensions.attributes, macro.xtext }⚓ |
| <zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||
| Module | transcr — Schema | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface. A graphic element contained by a zone represents the whole of the zone. A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface. A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element. | ||||||||
| Example | <surface ulx="14.54" uly="16.14" lrx="0"
lry="0">
<graphic url="stone.jpg"/>
<zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375
11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
</surface> This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]]. | ||||||||
| Example | <facsimile>
<surface ulx="50" uly="20" lrx="400"
lry="280">
<zone ulx="0" uly="0" lrx="500" lry="321">
<graphic url="graphic.png"/>
</zone>
</surface>
</facsimile> This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains. | ||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.graphicLike"/>
<classRef key="model.global"/>
<elementRef key="surface"/>
<classRef key="model.linePart"/>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element zone
{
att.global.attributes,
att.coordinated.attributes,
att.typed.attributes,
att.written.attributes,
attribute rotate { text }?,
(
text
| model.gLike
| model.graphicLike
| model.global
| surface
| model.linePart
)*
}⚓ | ||||||||
| model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses] | |
| Module | tei — Schema |
| Used by | |
| Members | model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[addName forename surname] model.placeStateLike[model.placeNamePart[country district geogName placeName region settlement]] idno] addrLine postCode street |
| model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure] | |
| Module | tei — Schema |
| Used by | |
| Members | address email |
| model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts] | |
| Module | tei — Schema |
| Used by | |
| Members | model.quoteLike[cit quote] |
| model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei — Schema |
| Used by | |
| Members | licence |
| model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei — Schema |
| Used by | |
| Members | bibl biblStruct listBibl msDesc |
| model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei — Schema |
| Used by | |
| Members | model.imprintPart[biblScope distributor pubPlace publisher] model.respLike[author editor funder principal respStmt sponsor] availability bibl citedRange decoNote edition explicit extent incipit listRelation msIdentifier relatedItem series textLang |
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | model.divPart[model.lLike[l] model.pLike[p] lg] model.inter[model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listPerson listPlace listRelation table] model.oddDecl model.stageLike] include q |
| Note | This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
| model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates] | |
| Module | tei — Schema |
| Used by | |
| Members | date |
| model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | model.lLike[l] model.pLike[p] lg |
| Note | Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items. |
| model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei — Schema |
| Used by | |
| Members | model.divTopPart[model.headLike[head]] model.divWrapper |
| model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages] | |
| Module | tei — Schema |
| Used by | |
| Members | model.headLike[head] |
| model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times. | |
| Module | tei — Schema |
| Used by | |
| Members | interpretation |
| model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei — Schema |
| Used by | |
| Members | foreign term title |
| model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times. | |
| Module | tei — Schema |
| Used by | |
| Members | charDecl classDecl editorialDecl projectDesc |
| model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | model.global.edit[gap] model.global.meta model.milestoneLike[fw lb pb] model.noteLike[note] figure |
| model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | gap |
| model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei — Schema |
| Used by | |
| Members | hi q |
| model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
| Module | tei — Schema |
| Used by | |
| Members | model.emphLike[foreign term title] model.hiLike[hi q] |
| model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
| Module | tei — Schema |
| Used by | |
| Members | biblScope distributor pubPlace publisher |
| model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listPerson listPlace listRelation table] model.oddDecl model.stageLike |
| model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | model.emphLike[foreign term title] model.hiLike[hi q] model.pPart.data[model.addressLike[address email] model.dateLike[date] model.measureLike[depth dim geo height measure num width] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[addName forename surname] model.placeStateLike[model.placeNamePart[country district geogName placeName region settlement]] idno]] model.pPart.editorial[abbr am choice ex expan subst] model.pPart.msdesc[catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml[gi] model.ptrLike[ptr ref] |
| model.listLike groups list-like elements. [3.8. Lists] | |
| Module | tei — Schema |
| Used by | |
| Members | list listPerson listPlace listRelation table |
| model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements] | |
| Module | tei — Schema |
| Used by | |
| Members | fw lb pb |
| model.msItemPart groups elements which can appear within a manuscript item description. | |
| Module | tei — Schema |
| Used by | |
| Members | model.biblLike[bibl biblStruct listBibl msDesc] model.msQuoteLike[colophon explicit finalRubric incipit rubric title] model.quoteLike[cit quote] model.respLike[author editor funder principal respStmt sponsor] decoNote filiation idno msItem msItemStruct textLang |
| model.nameLike groups elements which name or refer to a person, place, or organization. | |
| Module | tei — Schema |
| Used by | |
| Members | model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[addName forename surname] model.placeStateLike[model.placeNamePart[country district geogName placeName region settlement]] idno |
| Note | A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
| model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei — Schema |
| Used by | |
| Members | name orgName persName |
| Note | This class is used in the content model of elements which reference names of people or organizations. |
| model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing] | |
| Module | tei — Schema |
| Used by | |
| Members | note |
| model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. Place Names] | |
| Module | tei — Schema |
| Used by | |
| Members | geogFeat |
| model.pLike groups paragraph-like elements. | |
| Module | tei — Schema |
| Used by | additional availability binding bindingDesc custodialHist decoDesc editionStmt editorialDecl encodingDesc handDesc history interpretation langUsage layoutDesc listRelation model.divPart msContents msDesc msFrag msItem msItemStruct msPart objectDesc person physDesc place projectDesc publicationStmt recordHist scriptDesc seal sealDesc sourceDesc supportDesc typeDesc |
| Members | p |
| model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei — Schema |
| Used by | |
| Members | model.addressLike[address email] model.dateLike[date] model.measureLike[depth dim geo height measure num width] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[addName forename surname] model.placeStateLike[model.placeNamePart[country district geogName placeName region settlement]] idno] |
| model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description] | |
| Module | tei — Schema |
| Used by | |
| Members | catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark |
| model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names] | |
| Module | namesdates — Schema |
| Used by | |
| Members | addName forename surname |
| model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name. | |
| Module | tei — Schema |
| Used by | |
| Members | persName |
| Note | These characteristics of an individual are typically a consequence of their own action or that of others. |
| model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description] | |
| Module | tei — Schema |
| Used by | |
| Members | model.biblLike[bibl biblStruct listBibl msDesc] model.eventLike model.persStateLike[persName] idno name |
| model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements] | |
| Module | tei — Schema |
| Used by | |
| Members | gi |
| model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source. | |
| Module | msdescription — Schema |
| Used by | |
| Members | accMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc |
| model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names] | |
| Module | tei — Schema |
| Used by | |
| Members | country district geogName placeName region settlement |
| model.placeStateLike groups elements which describe changing states of a place. | |
| Module | tei — Schema |
| Used by | |
| Members | model.placeNamePart[country district geogName placeName region settlement] |
| model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times. | |
| Module | tei — Schema |
| Used by | |
| Members | langUsage textClass |
| model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
| Module | tei — Schema |
| Used by | |
| Members | ptr ref |
| model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei — Schema |
| Used by | |
| Members | authority distributor publisher |
| Note | The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element. See also model.publicationStmtPart.detail. |
| model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei — Schema |
| Used by | |
| Members | model.ptrLike[ptr ref] address availability date idno pubPlace |
| Note | A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
| model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Members | facsimile text |
| model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |
| Module | tei — Schema |
| Used by | |
| Members | seg |
| Note | The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header. |
| model.teiHeaderPart groups high level elements which may appear more than once in a TEI header. | |
| Module | tei — Schema |
| Used by | |
| Members | encodingDesc include profileDesc |
| model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages] | |
| Module | tei — Schema |
| Used by | |
| Members | graphic |
| att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations. | |||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||
| Members | note | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
<!-- elsewhere in the document -->
<noteGrp targetEnd="#A55234">
<note xml:lang="en"> Quatuor Tempora, so called dry fast days.
</note>
<note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
</note>
</noteGrp> | ||||||||||||||||||
| att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | att.ascribed.directed[q] change | ||||||||||
| Attributes |
| ||||||||||
| att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | q | ||||||||||
| Attributes |
| ||||||||||
| att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone Elements] | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | lb pb | ||||||||||
| Attributes |
| ||||||||||
| att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer. | |||||||||
| Module | tei — Schema | ||||||||
| Members | ptr ref term | ||||||||
| Attributes |
| ||||||||
| att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||
| Module | tei — Schema | ||||||||||||||
| Members | date origDate | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||
| Members | att.naming[att.personal[addName forename name orgName persName placeName surname] author collection country district editor geogFeat geogName institution origPlace pubPlace region repository settlement] authority catDesc date distributor funder material objectType principal publisher relation resp respStmt sponsor term title | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Example | In this contrived example, a canonical reference to the same organisation is provided in four different ways. <author n="1">
<name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="2">
<name ref="nzvn:427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="3">
<name ref="./named_entities.xml#o427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="4">
<name key="name-427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author> The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available. | ||||||||||||||||||||
| Note | The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange. These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange. | ||||||||||||||||||||
| att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes] | |||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||
| Members | biblScope citedRange | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system. | |||||||||||||||||||||||||||||||||||||
| Module | transcr — Schema | ||||||||||||||||||||||||||||||||||||
| Members | surface zone | ||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||
| att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes] | |||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||
| Members | damage | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates] | |||||||
| Module | tei — Schema | ||||||
| Members | acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region relation resp seal settlement sponsor stamp title | ||||||
| Attributes |
| ||||||
| Note | This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. | ||||||
| att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | namesdates — Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.datable[acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region relation resp seal settlement sponsor stamp title] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||||||||||||||||
| Module | namesdates — Schema | ||||||||||||||||||||||||||||||||||
| Members | att.datable[acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region relation resp seal settlement sponsor stamp title] | ||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||
| Note | The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar. If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is, <date when-iso="2007-06-01" dur-iso="P8D"/> indicates the same time period as <date when-iso="2007-06-01/P8D"/> In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading. | ||||||||||||||||||||||||||||||||||
| att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||||||||
| Members | att.datable[acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region relation resp seal settlement sponsor stamp title] | ||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//*[not(self::tei:locus or self::tei:biblScope or self::tei:citedRange)]
[(@notBefore and @notAfter) or (@from and @to)]">
<sch:let name="f"
value="(@notBefore,@from)[1]"/>
<sch:let name="t"
value="(@notAfter,@to)[1]"/>
<sch:let name="bothdates"
value="$f castable as xs:date and $t castable as xs:date"/>
<sch:let name="bothyears"
value="$f castable as xs:integer and $t castable as xs:integer"/>
<sch:let name="fd"
value="if ($bothdates) then xs:date($f) else ()"/>
<sch:let name="td"
value="if ($bothdates) then xs:date($t) else ()"/>
<sch:let name="fy"
value="if ($bothyears) then xs:integer($f) else ()"/>
<sch:let name="ty"
value="if ($bothyears) then xs:integer($t) else ()"/>
<sch:report test="($bothdates and $fd gt $td) or ($bothyears and $fy gt $ty)"
role="error"> The date range <sch:value-of select="$f"/>–<sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> is not valid. </sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@when]">
<sch:report test="@notBefore|@notAfter|@from|@to"
role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@from]">
<sch:report test="@notBefore"
role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@to]">
<sch:report test="@notAfter"
role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||||||||
| Example | <date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date> | ||||||||||||||||||||||||||||||||||||
| Note | The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar. The most commonly-encountered format for the date portion of a temporal attribute is Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used. | ||||||||||||||||||||||||||||||||||||
| att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values] | |||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||
| Members | att.segLike[seg] category taxonomy | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.<fs>
<f name="POS"
datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
<symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
value="NN"/>
</f>
<!-- ... -->
</fs> ‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]]. <fs>
<f name="POS" fVal="#commonNoun"/>
<!-- ... -->
</fs> The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories. <fvLib n="POS values">
<symbol xml:id="commonNoun" value="NN"
datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
<symbol xml:id="properNoun" value="NP"
datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>
<!-- ... -->
</fvLib> Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value. | ||||||||||||||||||
| Example | In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above. <gramGrp>
<pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos>
</gramGrp> Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>: <tagsDecl partial="true">
<!-- ... -->
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="pos"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>
<tagUsage gi="case"
targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage>
<!-- ... -->
</namespace>
</tagsDecl> Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below: <listPrefixDef>
<prefixDef ident="ccr" matchPattern="pos"
replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
<prefixDef ident="ccr" matchPattern="adj"
replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>
</listPrefixDef>
<!-- ... -->
<entry>
<!--...-->
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos datcat="ccr:pos"
valueDatcat="ccr:adj">adj</pos>
</gramGrp>
<!--...-->
</entry> This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>. | ||||||||||||||||||
| Example | The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology. <encodingDesc>
<!-- ... -->
<classDecl>
<!-- ... -->
<taxonomy xml:id="UD-SYN"
datcat="https://universaldependencies.org/u/dep/index.html">
<desc>
<term>UD syntactic relations</term>
</desc>
<category xml:id="acl"
valueDatcat="https://universaldependencies.org/u/dep/acl.html">
<catDesc>
<term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>
</category>
<category xml:id="acl_relcl"
valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">
<catDesc>
<term>acl:relcl</term>: relative clause modifier</catDesc>
</category>
<category xml:id="advcl"
valueDatcat="https://universaldependencies.org/u/dep/advcl.html">
<catDesc>
<term>advcl</term>: Adverbial clause modifier</catDesc>
</category>
<!-- ... -->
</taxonomy>
</classDecl>
</encodingDesc> The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly. | ||||||||||||||||||
| Example | The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object. <fDecl name="POS"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
<fDescr>part of speech (morphosyntactic category)</fDescr>
<vRange>
<vAlt>
<symbol value="NN"
datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>
<symbol value="NP"
datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>
<!-- ... -->
</vAlt>
</vRange>
</fDecl> Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element. | ||||||||||||||||||
| Example | The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>
<classDecl>
<taxonomy xml:id="domains">
<!--...-->
<category xml:id="domain.medical_and_health_sciences">
<catDesc xml:lang="en">Medical and Health Sciences</catDesc>
<catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>
<category xml:id="domain.medical_and_health_sciences.medicine"
valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">
<catDesc xml:lang="en">
<term>Medicine</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
<catDesc xml:lang="pt">
<term>Medicina</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
</category>
</category>
<!--...-->
</taxonomy>
</classDecl>
</encodingDesc>
<!--
inside an <entry> element: -->
<usg type="domain"
valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg> In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH). | ||||||||||||||||||
| Note | The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container. A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute. In a TEI XML example of two equivalent serializations expressing the name-value pair The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech). The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects. Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example. Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices. | ||||||||||||||||||
| att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text] | |||||||||
| Module | tei — Schema | ||||||||
| Members | availability bibl biblStruct editorialDecl interpretation langUsage listBibl listPerson listPlace projectDesc sourceDesc textClass | ||||||||
| Attributes |
| ||||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true. | ||||||||
| att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text] | |||||||
| Module | tei — Schema | ||||||
| Members | body div facsimile geo graphic lg msDesc p ptr ref surface surfaceGrp term text | ||||||
| Attributes |
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. | ||||||
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||||||||||
| Members | att.damaged[damage] add date del depth dim dimensions ex gap geogFeat height origDate subst supplied unclear width | ||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
| att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure] | |||||||||||||||||
| Module | tei — Schema | ||||||||||||||||
| Members | div lg | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
| Module | tei — Schema | ||||||||
| Members | bibl biblStruct change msDesc revisionDesc | ||||||||
| Attributes |
| ||||||||
| Example | <revisionDesc status="published">
<change when="2010-10-21"
status="published"/>
<change when="2010-10-02" status="cleared"/>
<change when="2010-08-02"
status="embargoed"/>
<change when="2010-05-01" status="frozen"
who="#MSM"/>
<change when="2010-03-01" status="draft"
who="#LB"/>
</revisionDesc> | ||||||||
| att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei — Schema | ||||||||||||||||
| Members | att.transcriptional[add del subst] am corr date ex expan gap geogFeat geogName name orgName origDate origPlace origin persName person place placeName reg relation supplied unclear | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Note | The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc. Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned. | ||||||||||||||||
| att.edition provides attributes identifying the source edition from which some encoded feature derives. | |||||||||||||
| Module | tei — Schema | ||||||||||||
| Members | lb pb | ||||||||||||
| Attributes |
| ||||||||||||
| Example | <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> | ||||||||||||
| Example | <listBibl>
<bibl xml:id="stapledon1937">
<author>Olaf Stapledon</author>,
<title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
</bibl>
<bibl xml:id="stapledon1968">
<author>Olaf Stapledon</author>,
<title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
</bibl>
</listBibl>
<!-- ... -->
<p>Looking into the future aeons from the supreme moment of
the cosmos, I saw the populations still with all their
strength maintaining the<pb n="411" edRef="#stapledon1968"/>essentials of their ancient culture,
still living their personal lives in zest and endless
novelty of action, … I saw myself still
preserving, though with increasing difficulty, my lucid
con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p> | ||||||||||||
| att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy. | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | att.divLike[div lg] att.segLike[seg] l p | ||||||||||
| Attributes |
| ||||||||||
| att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||||||||||||||||
| Members | TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone | ||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||
| att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles] | |||||||
| Module | transcr — Schema | ||||||
| Members | att.global[TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] | ||||||
| Attributes |
| ||||||
| att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | linking — Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.global[TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators] | |||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||
| Members | att.global[TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="*[@rend]">
<sch:report test="self::tei:hi and not(every $r in tokenize(@rend, '\s+')[string-length()
gt 0] satisfies $r = ('bold', 'italic', 'smallcaps', 'roman', 'superscript',
'subscript', 'underline', 'overline', 'strikethrough'))"
role="info"> Any values can be used in rend attributes, but
the web site currently only supports combinations of: bold,
italic, roman, smallcaps, superscript, subscript, underline,
overline, and strikethrough. </sch:report>
<sch:report test="self::tei:list and not(every $r in tokenize(@rend, '\s+')[string-length()
gt 0] satisfies $r = ('numbered', 'ordered', 'ol', 'bulleted', 'unordered',
'ul'))"
role="info"> Any values can be used in rend attributes, but
the web site currently only supports combinations of:
numbered, ordered, ol, bulleted, unordered, and ul. </sch:report>
<sch:assert test="self::tei:hi or self::tei:list"
role="info"> The web site currently only supports rend attributes for hi
and list elements. Using it on <sch:value-of select="name(.)"/> elements is valid but will be
ignored. </sch:assert>
</sch:rule>
<sch:rule context="*[@rendition or @style]">
<sch:assert test="false()" role="info"> The web site currently
ignores rendition and style attributes. </sch:assert>
</sch:rule> | ||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@key]">
<sch:assert test="string-length(normalize-space(string())) gt 1"
role="warn"> Elements with key attributes should have some
content (because they will be displayed as links, and links
need text for readers to click on.) </sch:assert>
</sch:rule> | ||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:height|tei:width">
<sch:assert test="string-length(normalize-space(string())) gt 0"
role="warn"> For dimensions the website displays the content
of height and width elements. Attribute values are not
displayed. Empty elements will not display correctly.
</sch:assert>
</sch:rule> | ||||||||||||||||||||||||||||||
| att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei — Schema | ||||||||||||||
| Members | att.global[TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] | ||||||||||||||
| Attributes |
| ||||||||||||||
| Example | Blessed are the
<choice>
<sic>cheesemakers</sic>
<corr resp="#editor" cert="high">peacemakers</corr>
</choice>: for they shall be called the children of God. | ||||||||||||||
| Example |
<!-- in the <text> ... --><lg>
<!-- ... -->
<l>Punkes, Panders, baſe extortionizing
sla<choice>
<sic>n</sic>
<corr resp="#JENS1_transcriber">u</corr>
</choice>es,</l>
<!-- ... -->
</lg>
<!-- in the <teiHeader> ... -->
<!-- ... -->
<respStmt xml:id="JENS1_transcriber">
<resp when="2014">Transcriber</resp>
<name>Janelle Jenstad</name>
</respStmt> | ||||||||||||||
| att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing] | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | att.global[TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category cell change charDecl choice cit citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor editorialDecl email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw g gap geo geogFeat geogName gi glyph graphic handDesc handNote head height heraldry hi history idno imprint incipit institution interpretation item keywords l label langUsage language layout layoutDesc lb lg licence list listBibl listPerson listPlace listRelation locus locusGrp mapping material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName person physDesc place placeName postCode principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem relation repository resp respStmt revisionDesc row rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates table taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] | ||||||||||
| Attributes |
| ||||||||||
| Example | <p>
<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
term.</quote>
<!-- ... -->
</p> | ||||||||||
| Example | <p>
<!-- ... -->
<quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
less we seem to know.</quote>
<!-- ... -->
</p>
<!-- ... -->
<bibl xml:id="chicago_15_ed">
<title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.
</bibl> | ||||||||||
| Example | <elementRef key="p" source="tei:2.0.1"/> Include in the schema an element named <p> available from the TEI P5 2.0.1 release. | ||||||||||
| Example | <schemaSpec ident="myODD"
source="mycompiledODD.xml">
<!-- further declarations specifying the components required -->
</schemaSpec> Create a schema using components taken from the file mycompiledODD.xml. | ||||||||||
| att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands] | |||||||||||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||||||||||
| Members | handNote scriptNote typeNote | ||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
| Note | Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied. | ||||||||||||||||||||||||||||||||||||||
| att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy. | |||||||
| Module | tei — Schema | ||||||
| Members | att.media[graphic] ptr ref | ||||||
| Attributes |
| ||||||
| Example | In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8. <ref mimeType="application/tei+xml; charset=UTF-8"
target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/> | ||||||
| Note | This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list. | ||||||
| att.measurement provides attributes to represent a regularized or normalized measurement. | |||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||
| Members | measure | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@unitRef]">
<sch:report test="@unit" role="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||
| Note | This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system. <l>So weren't you gonna buy <measure quantity="0.5" unit="gal"
commodity="ice cream">half
a gallon</measure>, baby</l>
<l>So won't you go and buy <measure quantity="1.893" unit="L"
commodity="ice cream">half
a gallon</measure>, baby?</l> The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters. | ||||||||||||||||||||||||||||||
| att.media provides attributes for specifying display and related properties of external media. | |||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||
| Members | graphic | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements] | |||||||
| Module | msdescription — Schema | ||||||
| Members | msContents msItem msItemStruct | ||||||
| Attributes |
| ||||||
| att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content] | |||||||
| Module | msdescription — Schema | ||||||
| Members | colophon explicit finalRubric incipit msContents msItem msItemStruct quote rubric | ||||||
| Attributes |
| ||||||
| Note | In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole. | ||||||
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms] | |||||||||||||||
| Module | tei — Schema | ||||||||||||||
| Members | att.personal[addName forename name orgName persName placeName surname] author collection country district editor geogFeat geogName institution origPlace pubPlace region repository settlement | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.notated provides attributes to indicate any specialised notation used for element content. | |||||||
| Module | tei — Schema | ||||||
| Members | formula quote seg | ||||||
| Attributes |
| ||||||
| att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names] | |||||||||||||||
| Module | tei — Schema | ||||||||||||||
| Members | addName forename name orgName persName placeName surname | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions] | |||||||||||||
| Module | tei — Schema | ||||||||||||
| Members | add figure fw head label note | ||||||||||||
| Attributes |
| ||||||||||||
| att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References] | |||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||
| Members | citedRange licence locus note ptr ref term | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||||||||||
| Members | att.dimensions[att.damaged[damage] add date del depth dim dimensions ex gap geogFeat height origDate subst supplied unclear width] measure num | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//*[(@atLeast and @atMost) or (@min and @max)]">
<sch:let name="f"
value="(@atLeast,@min)[1]"/>
<sch:let name="t" value="(@atMost,@max)[1]"/>
<sch:let name="bothnumbers"
value="$f castable as xs:float and $t castable as xs:float"/>
<sch:let name="fv"
value="if ($bothnumbers) then xs:float($f) else ()"/>
<sch:let name="tv"
value="if ($bothnumbers) then xs:float($t) else ()"/>
<sch:report test="$bothnumbers and $fv gt $tv"
role="warn"> The
numerical range <sch:value-of select="$f"/>–<sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> may
not be valid. </sch:report>
</sch:rule> | ||||||||||||||||||||||||||||||
| Example | The MS. was lost in transmission by mail from <del rend="overstrike">
<gap reason="illegible"
extent="one or two letters" atLeast="1" atMost="2" unit="chars"/>
</del> Philadelphia to the Graphic office, New York.
| ||||||||||||||||||||||||||||||
| Example | Americares has been supporting the health sector in Eastern
Europe since 1986, and since 1992 has provided <measure atLeast="120000000" unit="USD"
commodity="currency">more than
$120m</measure> in aid to Ukrainians.
| ||||||||||||||||||||||||||||||
| att.resourced provides attributes by which a resource (such as an externally held media file) may be located. | |||||||
| Module | tei — Schema | ||||||
| Members | graphic | ||||||
| Attributes |
| ||||||
| att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |||||||||
| Module | tei — Schema | ||||||||
| Members | seg | ||||||||
| Attributes |
| ||||||||
| att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei — Schema | ||||||||||
| Members | bibl biblStruct idno item list listBibl listPerson listPlace listRelation msDesc person place relation term | ||||||||||
| Attributes |
| ||||||||||
| att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes] | |||||||||
| Module | tei — Schema | ||||||||
| Members | lb pb | ||||||||
| Attributes |
| ||||||||
| Note | The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself. | ||||||||
| att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music] | |||||||||||||||||||||||||||||||
| Module | figures — Schema | ||||||||||||||||||||||||||||||
| Members | cell row | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information] | |||||||||||||||||
| Module | tei — Schema | ||||||||||||||||
| Members | gap | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions] | |||||||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||||||
| Members | add del subst | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document. | |||||||||
| Module | tagdocs — Schema | ||||||||
| Members | desc | ||||||||
| Attributes |
| ||||||||
| att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei — Schema | ||||||||||||||||||
| Members | TEI abbr accMat add addName altIdentifier am bibl biblStruct change cit collection corr country custEvent damage date decoNote del desc dim dimensions district div explicit figure filiation finalRubric forename fw g geogFeat geogName graphic head idno incipit label layout lb lg list listBibl listPerson listPlace listRelation locus mapping material measure msDesc msFrag msName msPart name note num orgName origDate origPlace pb persName place placeName provenance ptr quote ref reg region relatedItem relation rubric seal seg settlement signatures stamp surface surfaceGrp surname table term text title zone | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
</sch:rule> | ||||||||||||||||||
| Note | When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
| att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes] | |||||||
| Module | tei — Schema | ||||||
| Members | att.damaged[damage] att.transcriptional[add del subst] div figure fw head hi label note p seg text zone | ||||||
| Attributes |
| ||||||
| macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.inter"/>
</alternate>
</content>
⚓ |
| Declaration | macro.limitedContent = ( text | model.limitedPhrase | model.inter )*⚓ |
| macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.paraPart"/>
</alternate>
</content>
⚓ |
| Declaration | macro.paraContent = ( text | model.paraPart )*⚓ |
| macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
| Module | tei — Schema |
| Used by | abbr addName addrLine author biblScope catchwords citedRange colophon country distributor district edition editor email expan explicit extent finalRubric foreign forename fw geogFeat geogName heraldry incipit label material measure name num objectType orgName origPlace persName placeName pubPlace publisher region rubric secFol settlement stamp street surname term watermark |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.attributable"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration | macro.phraseSeq = ( text | model.gLike | model.attributable | model.phrase | model.global )*⚓ |
| macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models] | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration | macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*⚓ |
| macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.divPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration |
macro.specialPara =
(
text
| model.gLike
| model.phrase
| model.inter
| model.divPart
| model.global
)*⚓ |
| macro.xtext (extended text) defines a sequence of character data and gaiji elements. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
</alternate>
</content>
⚓ |
| Declaration | macro.xtext = ( text | model.gLike )*⚓ |
| teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<valList type="closed">
<valItem ident="high"/>
<valItem ident="medium"/>
<valItem ident="low"/>
<valItem ident="unknown"/>
</valList>
</content>
⚓ |
| Declaration | teidata.certainty = "high" | "medium" | "low" | "unknown"⚓ |
| Note | Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. |
| teidata.count defines the range of attribute values used for a non-negative integer value used as a count. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="nonNegativeInteger"/>
</content>
⚓ |
| Declaration | teidata.count = xsd:nonNegativeInteger⚓ |
| Note | Any positive integer value or zero is permitted |
| teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
⚓ |
| Declaration |
teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓ |
| Example | <time dur-iso="PT0,75H">three-quarters of an hour</time> |
| Example | <date dur-iso="P1,5D">a day and a half</date> |
| Example | <date dur-iso="P14D">a fortnight</date> |
| Example | <time dur-iso="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
| teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="duration"/>
</content>
⚓ |
| Declaration | teidata.duration.w3c = xsd:duration⚓ |
| Example | <time dur="PT45M">forty-five minutes</time> |
| Example | <date dur="P1DT12H">a day and a half</date> |
| Example | <date dur="P7D">a week</date> |
| Example | <time dur="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the For complete details, see the W3C specification. |
| teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
| Module | tei — Schema |
| Used by | teidata.gender teidata.sexElement:
|
| Content model |
<content>
<dataRef key="teidata.word"/>
</content>
⚓ |
| Declaration | teidata.enumerated = teidata.word⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
| teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | teidata.gender = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms). |
| teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="language"/>
<valList>
<valItem ident=""/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | teidata.language = xsd:language | ( "" )⚓ |
| Note | The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice. A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications. Second, an entire language tag can consist of only a private use subtag. These tags start with Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
| teidata.name defines the range of attribute values expressed as an XML Name. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="Name"/>
</content>
⚓ |
| Declaration | teidata.name = xsd:Name⚓ |
| Note | Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
| teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef restriction="\S+" name="anyURI"/>
</content>
⚓ |
| Declaration |
teidata.namespace = xsd:anyURI { pattern = "\S+" }⚓ |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax |
| teidata.numeric defines the range of attribute values used for numeric values. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<alternate>
<dataRef name="double"/>
<dataRef name="token"
restriction="(\-?[\d]+/\-?[\d]+)"/>
<dataRef name="decimal"/>
</alternate>
</content>
⚓ |
| Declaration |
teidata.numeric =
xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal⚓ |
| Note | Any numeric value, represented as a decimal number, in floating point format, or as a ratio. To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3. A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2. |
| teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
⚓ |
| Declaration |
teidata.outputMeasurement =
token
{
pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
}⚓ |
| Example | <figure>
<head>The TEI Logo</head>
<figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
background.</figDesc>
<graphic height="600px" width="600px"
url="http://www.tei-c.org/logos/TEI-600.jpg"/>
</figure> |
| Note | These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft. |
| teidata.pattern defines attribute values which are expressed as a regular expression. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="token"/>
</content>
⚓ |
| Declaration | teidata.pattern = token⚓ |
| Note | A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern WikipediaH(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema. |
| teidata.point defines the data type used to express a point in cartesian space. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
⚓ |
| Declaration |
teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }⚓ |
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="400" lry="280">
<zone points="220,100 300,210 170,250 123,234">
<graphic url="handwriting.png"/>
</zone>
</surface>
</facsimile> |
| Note | A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not. |
| teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<dataRef restriction="\S+" name="anyURI"/>
</content>
⚓ |
| Declaration |
teidata.pointer = xsd:anyURI { pattern = "\S+" }⚓ |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, |
| teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef key="teidata.probability"/>
<dataRef key="teidata.certainty"/>
</alternate>
</content>
⚓ |
| Declaration | teidata.probCert = teidata.probability | teidata.certainty⚓ |
| teidata.probability defines the range of attribute values expressing a probability. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="double"/>
</content>
⚓ |
| Declaration | teidata.probability = xsd:double⚓ |
| Note | Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. |
| teidata.sex defines the range of attribute values used to identify the sex of an organism. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | teidata.sex = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. |
| teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</alternate>
</content>
⚓ |
| Declaration |
teidata.temporal.iso =
xsd:date
| xsd:gYear
| xsd:gMonth
| xsd:gDay
| xsd:gYearMonth
| xsd:gMonthDay
| xsd:time
| xsd:dateTime
| token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format. |
| teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
</alternate>
</content>
⚓ |
| Declaration | teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
| teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"
restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
<dataRef name="dateTime"
restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
</alternate>
</content>
⚓ |
| Declaration |
teidata.temporal.working =
xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
| xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z. |
| teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="string"/>
</content>
⚓ |
| Declaration | teidata.text = string⚓ |
| Note | Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
| teidata.truthValue defines the range of attribute values used to express a truth value. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<dataRef name="boolean"/>
</content>
⚓ |
| Declaration | teidata.truthValue = xsd:boolean⚓ |
| Note | The possible values of this datatype are 1 or true, or 0 or false. This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue. |
| teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="nonNegativeInteger"/>
<valList type="closed">
<valItem ident="unbounded"/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )⚓ |
| teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei — Schema |
| Used by | Element:
|
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
⚓ |
| Declaration |
teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }⚓ |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
| teidata.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
⚓ |
| Declaration |
teidata.versionNumber =
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }⚓ |
| teidata.word defines the range of attribute values expressed as a single word or token. | |
| Module | tei — Schema |
| Used by | teidata.enumeratedElement:
|
| Content model |
<content>
<dataRef name="token"
restriction="[^\p{C}\p{Z}]+"/>
</content>
⚓ |
| Declaration |
teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
| teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="boolean"/>
<valList>
<valItem ident="unknown"/>
<valItem ident="inapplicable"/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )⚓ |
| Note | In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
| teidata.xpath defines attribute values which contain an XPath expression. | |
| Module | tei — Schema |
| Used by | |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Declaration | teidata.xpath = text⚓ |
| Note | Any XPath expression using the syntax defined in 6.2.. When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP. |